.Net Remoting - concurrent connections limitation
Posted on 2005-04-10
I'm using .Net Remoting to connect between processes on different machines, TcpChannel SingleCall mode, Windows2000 Server. I have several clients applications with multithreads in each clients, it can go up to 100 concurrent connections to a single server. Every now and then one of the connections failed with the following exception: "No connection could be made because the target machine actively refused it". Does the .Net Remoting framework has limitation on the number of concurrent connections to a single .Net Remoting server?