Existing connection is closed when creating new TCP connections
I have a TCP listener service that clients are connecting to. Lately I started getting this disconnect related error. I connect about 20 clients to it and the connection works fine. But when I connect 10 more clients to the service, previous connections fail with error 10053 or 10054.
It used to be used for 100 clients, but I'm not sure what the problem might be. The service and clients are running on Windows Server 2003 because I found that Windows XP has a known issue with multiple TCP connections (referring to 10053).
source to share
Well, the errors you get are very different.
10053 - WSAECONNABORTED - The connection was interrupted. This is usually due to a problem in the application stack (although it does happen sometimes).
10054 - WSAECONNRESET. The connection has been reset by a peer. This is usually a problem on the other side of the connection.
How do you test this? Are customers associated with this service? If so, you should keep track of what is happening on the client side when you receive 10054.
Also, it could be due to network issues not related to your software (directly). Have there been any changes to the network infrastructure you are working on?
source to share
I doubt if this is a network problem, or you will probably see this happening when the first 20 clients connect. Just a shot in the dark, but how do you deal with these connections? Are you using some sort of array or collection? Could you accidentally re-establish existing connections to new connections, causing system craze?