[Mono-bugs] [Bug 74618][Cri] Changed - The error is generated when a remoting call is made from a client

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by flashdict@gmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=74618

--- shadow/74618	2005-04-16 14:35:13.000000000 -0400
+++ shadow/74618.tmp.26265	2005-04-16 20:33:21.000000000 -0400
@@ -114,6 +114,33 @@
 magic number - I can get up to 250 executions before faulting.
 
   I'm working on building absolute latest mono now, will try again
 afterwards.
 
 HTH.  
+
+------- Additional Comments From flashdict@gmail.com  2005-04-16 20:33 -------
+Second update, running now against r43128, I've tried several things
+which may help to narrow this down.
+
+1. Compiled with csc, run against .NET CLI - ok.
+
+2. Compiled with mcs and System.Runtime.Remoting, run against .NET - ok.
+
+3. Compiled with csc or mcs and running Server under .NET CLI - ok.
+(running only client under mono)
+
+4. Compiled with mcs or csc, running Server under Mono, this sometimes
+fails after 1-250 connections, but sometimes it works fine (I have 300
+dlls in the directory)
+
+So, the server is apparantly breaking the connection when run under
+mono, but it never throws any exception.  Only the client gives us
+information about the error, which is WinError 10053.
+
+(Note, Mono's System.ComponentModel.Win32Exception doesn't define this
+error, needs a little patch.)
+
+So, I'm thinking this is somewhere in the runtime then, given that the
+code runs ok whether compiled by mono or mcs, as long as the server is
+running .NET.  Yes?
+