[Mono-bugs] [Bug 70700][Nor] New - Maximum connections with Remoting/TcpChannel

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 20 Dec 2004 14:43:09 -0500 (EST)

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 sebastien.robitaille@croesus.com.


--- shadow/70700	2004-12-20 14:43:09.000000000 -0500
+++ shadow/70700.tmp.15947	2004-12-20 14:43:09.000000000 -0500
@@ -0,0 +1,57 @@
+Bug#: 70700
+Product: Mono: Class Libraries
+Version: 1.0
+OS: Red Hat 9.0
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: CORLIB
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: sebastien.robitaille@croesus.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: Maximum connections with Remoting/TcpChannel
+Please fill in this template when reporting a bug, unless you know what 
+you are doing.
+Description of Problem:
+There are two maximum values defined in the TcpChannel implementation of 
+Mono that doesn't seem to exist in the MS.NET implementation:
+[TcpServerChannel.cs] TcpServerChannel._maxConcurrentConnections = 100
+[TcpConnectionPool.cs] TcpConnectionPool._maxOpenConnections = 50
+If you run a server and connect 101 clients to this server (on the same 
+host), the 101th Client will hang until one of the other clients 
+On the other side, if a simple client tries to connect more than 50 times 
+to the server, new connections past 50 will hang.
+For an code example of such a client and server, please refer to bug 
+Steps to reproduce the problem:
+1. Run a server that exposes an object through Remoting/Tcp 
+2. Connect 100 clients to this server (by calling a remote method of the 
+server in a loop for example).
+3. Connect the 101th and see that the client hangs.
+4. Do the same test on MS.NET and see that this limit does not exist or 
+is much higher.
+Actual Results:
+Expected Results:
+How often does this happen? 
+Additional Information: