A connection abort was caused internal to your host machine. The software caused a connection abort because there is no space on the socket's queue and the socket cannot receive further connections.
WinSock description: The error can occur when the local network system aborts a connection. This would occur if WinSock aborts an established connection after data retransmission fails (receiver never acknowledges data sent on a datastream socket).
TCP/IP scenario: A connection will timeout if the local system doesn't receive an (ACK)nowledgement for data sent. It would also timeout if a (FIN)ish TCP packet is not ACK'd (and even if the FIN is ACK'd, it will eventually timeout if a FIN is not returned).
It seems to happen more with WindowsXP and it seems also to be possibly related to Windows firewall settings. In any case the salient point is that the abort has originated inside the local machine.
I should add here that sometimes this message is quite legitimate, e.g. when writing extra data to a socket that has been closed at the other end without any attempt to read all the incoming data. In this circumstance you get this message rather than the more usual 'connection reset by peer' when both client and server are running on the same host.
I know this probably isn't a good solution and may not bhelp you but I had a similar problem with an applet communicating with a server. My destroy function quitted the connection to the server.
I had to send 2 commands to the server then disconnect. I regularly saw a problem at the server end. It troubled me so I wanted to resolve. I ended up putting a 500 millisecond sleep between the two commands and the socket shutdown and that did the trick.
I waited for a response from the server after each command sent so not sure why I had to put the sleeps in - but it cured problem anyway. But it always bugs me if I don't know why. Something to come back to when I am less busy.
That's strange, because the information is right here in this thread. I provided not just 'some information' but quite a lot of information, including several explanations for "software caused connection abort"', when I started the thread eight months ago.
I put it there to be read. Not for people to post their stupid reiterations of the problem, without even reading the thread to see if there might be an answer in it.