All-- We've built an application in .NET that makes use of MSMQ for extensive peer-to-peer communication. Everything worked well in our testing lab, but we ran into a problem once we moved to early beta.
Apparently, there is a limit of 10 incoming simultaneous connections via TCP/IP on Windows XP Pro. With eight machines in our testing lab, we didn't see the problem. But, the deployment environment is close to 300 machines. There are a couple of architectural solutions we can use to make this work properly (specifying peer groups that can communicate with each other,) but I was wondering if there wasn't an easier way. Is there a way to (programmatically or manually) raise the connection limit on Windows XP enough to let the whole domain intercommunicate or, Failing that, is there a way to make MSMQ connections more transitory? Currently, we open the channels of communication at the beginning of a session and leave it open until the sessions is over. Looking at the code, it should be possible to open the connection right before sending the message, send the message, then close the connection. How big of a performance hit would this be? I welcome all input. --Jekke =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
