• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1323
  • Last Modified:

.Net Remoting - concurrent connections limitation

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?

Thanks,
Michael.
0
Relegence
Asked:
Relegence
1 Solution
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now