Official reasons for Software caused connection abort socket write error

Question

Given this stack trace snippet     Caused by  java net SocketException    Software caused connection abort    socket write error  nbsp at   java net SocketOutputStream socketWrite0 Native   Method    I tried to answer the following questions    What code is throwing this exception   JVM  Tomcat  My code   What causes this exception to be thrown    Regarding  1    Sun s JVM source doesn t contain this exact message  but I think the text Software caused connection abort  socket write error is from the native implementation of SocketOutputStream   private native void socketWrite0 FileDescriptor fd  byte   b  int off                   int len  throws IOException    Regarding  2  My guess is that it is caused when the client has terminated the connection  before getting the full response  e g  sent a request  but before getting the full response  it got closed   terminated   offline   Questions    Are the above assumptions correct   1 and  2   Can this be diffrentiated from the situation   could not write to the client  due to a network error on the server side   or would that render the same error message  And most important  Is there an official document  e g from Sun  stating the above    I need to have a proof that this stack trace is the socket client s  fault   and there is nothing that the server could have done to avoid it   except catching the exception  or using a non Sun JVM SocketOutputStream  though both don t really avoid the fact the client has terminated

User · Answer

ssl client side will throw such exception in below situation(I had tested), :

server is asked to authenticate client certificate, but the client provide a certificate which Extended Key Usage donot support client auth.

User · Answer

In my case  I developped the client and the server side  and I have the exception        Cause   error marshalling arguments  nested exception is    java net SocketException  Software caused connection abort  socket   write error   when classes in client and server are different  I don t download server s classes  Interfaces  on the client  I juste add same files in the project  But the path must be exactly the same  For example  on the server project I have java rmi services packages with some serviceInterface and implementations  I have to create the same package on the client project  If I change it by java rmi server services for example  I get the above exception  Same exception if the interface version is different between client and server  even with an empty row added inadvertently     I think rmi makes a sort of hash of classes to check version     I don t know    If it could help

User · Answer

Have you checked the Tomcat source code and the JVM source   That may give you more help   I think your general thinking is good  I would expect a ConnectException in the scenario that you couldn t connect  The above looks very like it s client-driven

User · Answer

Closed connection in another client  In my case  the error was   java net SocketException  Software caused connection abort  recv failed   It was received in eclipse while debugging a java application accessing a H2 database  The source of the error was that I had initially opened the database with SQuirreL to check manually for integrity  I did use the flag to enable multiple connections to the same DB  i e  AUTO SERVER TRUE   so there was no problem connecting to the DB from java   The error appeared when  after a while --it is a long java process-- I decided to close SQuirreL to free resources  It appears as if SQuirreL were the one  owning  the DB server instance and that it was shut down with the SQuirreL connection   Restarting the Java application did not yield the error again   config   Windows 7 Eclipse Kepler SQuirreL 3 6 org h2 Driver ver 1 4 192

User · Answer

This error happened to me while testing my soap service with SoapUI client  basically I was trying to get a very big message   500kb  and SoapUI closed the connection by timeout      On SoapUI go to       File-- Preferences--Socket Timeout ms       and put a large value  such as 180000  3 minutes   this won t be the perfect fix for your issue because the file is in fact to large  but at least you will have a response

User · Answer

I was facing the same problem with wireMock while mocking the rest API calls  Earlier I was defining the server like this   WireMockServer wireMockServer   null    But it should be defined like as shown below    Rule  public WireMockRule wireMockRule   new WireMockRule 8089

User · Answer

My server was throwing this exception in the pass 2 days and I solved it by moving the disconnecting function with    outputStream close    inputStream close    Client close      To the end of the  listing thread  if it will helped anyone

User · Answer

The java net SocketException is thrown when there is an error creating or accessing a socket  such as TCP   This usually can be caused when the server has terminated the connection  without properly closing it   so before getting the full response  In most cases this can be caused either by the timeout issue  e g  the response takes too much time or server is overloaded with the requests   or the client sent the SYN  but it didn t receive ACK  acknowledgment of the connection termination   For timeout issues  you can consider increasing the timeout value   The Socket Exception usually comes with the specified detail message about the issue   Example of detailed messages       Software caused connection abort  recv failed    The error indicates an attempt to send the message and the connection has been aborted by your server  If this happened while connecting to the database  this can be related to using not compatible Connector J JDBC driver   Possible solution  Make sure you ve proper libraries drivers in your CLASSPATH     Software caused connection abort  connect    This can happen when there is a problem to connect to the remote  For example due to virus-checker rejecting the remote mail requests   Possible solution  Check Virus scan service whether it s blocking the port for the outgoing requests for connections     Software caused connection abort  socket write error    Possible solution  Make sure you re writing the correct length of bytes to the stream  So double check what you re sending  See this thread     Connection reset by peer  socket write error   Connection aborted by peer  socket write error   The application did not check whether keep-alive connection had been timed out on the server side   Possible solution  Ensure that the HttpClient is non-null before reading from the connection E13222 01    Connection reset by peer    The connection has been terminated by the peer  server      Connection reset    The connection has been either terminated by the client or closed by the server end of the connection due to request with the request   See  What  39 s causing my java net SocketException  Connection reset

User · Answer

This error can occur when the local network system aborts a   connection  such as when WinSock closes an established connection   after data retransmission fails  receiver never acknowledges data sent   on a datastream socket     See this MSDN article  See also Some information about  Software caused connection abort

User · Answer

In the situation explained below  client side will throw such an exception   The server is asked to authenticate client certificate  but the client provides a certificate which Extended Key Usage doesn t support client auth  so the server doesn t accept the client s certificate  and then it closes the connection

User · Answer

I was facing the same issue  Commonly This kind of error occurs due to client has closed its connection and server still trying to write on that client  So make sure that your client has its connection open until server done with its outputstream  And one more thing  Don t forgot to  close input and output stream   Hope this helps   And if still facing issue than brief your problem here in details

User · Answer

To prove which component fails I would monitor the TCP IP communication using wireshark and look who is actaully closing the port  also timeouts could be relevant

User · Answer

For anyone using simple Client Server programms and getting this error  it is a problem of unclosed  or closed to early  Input or Output Streams

User · Answer

I have seen this most often when a corporate firewall on a workstation laptop gets in the way  it kills the connection   eg  I have a server process and a client process on the same machine  The server is listening on all interfaces  0 0 0 0  and the client attempts a connection to the public home interface  note not the loopback interface 127 0 0 1    If the machine is has its network disconnected  eg wifi turned off  then the connection is formed  If the machine is connected to the corporate network  directly or vpn  then the connection is formed   However  if the machine is connected to a public wifi  or home network  then the firewall kicks in an kills the connection  In this situation connecting the client to the loopback interface works fine  just not to the home public interface   Hope this helps

[java] Official reasons for "Software caused connection abort: socket write error"

Examples related to java

Examples related to exception

Examples related to sockets

Examples related to tomcat

Examples related to stack-trace