This content has been marked as final. Show 8 replies
Presumably an editorial (vent) rather than a question? :)
yep, just writing it down in the certain knowledge that the only person who will ever search for it here will be me ;-)
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.
... which just indicates bugs in the platform's TCP implementation.
java.net.SocketException: Software caused connection abort: recv failed
i found this error on TCP/IP messaging on windoz XP. i really do not have any idea how this error could be happened.
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.
Which is what these forums are for.
Obviously I was wasting my time.
Obviously I was wasting my time.Which you probably at least suspected when you posted it, but, like the glutton for punishment that we all are, you posted it anyway. ;-)
We still thank you, though.