Do your server-side methods do long-running cpu intensive operations? Or do they do things that naturally include some blocking (like performing I/O, grabbing locks, etc)? I ask because the remoting infrastructure uses I/O completion ports to manage the thread pool in such a way that long-running, cpu intensive operations performed by server-side methods can cause this behavior (especially if a server-side method gets into an infinite loop that never blocks). But if you're threads are not doing long-running, cpu intensive operations, than I don't want to go into the details if you have a different problem altogether :-)
-Mike http://staff.develop.com/woodring http://www.develop.com/devresources ----- Original Message ----- From: "Manuel Costa" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 29, 2002 10:36 AM Subject: [ADVANCED-DOTNET] singleton server problem > Hi, > > Is there a limit for the number of simultaneous calls to a remote object > registered as singleton? > I have an application with several servers and several clients per server. > After some amount of simultaneous calls to the servers they stop responding, > blocking any client call. When a client invokes a method it will stay > blocked and if i try to debug at the server side by putting a breakpoint in > the called method, nothing will happen. Is there any reasonable explanation > for this? > > Manuel > > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
