Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    via GitHub by nathandunn

    Nginx does not handle websocket requests. Configure nginx proxy for websockets.

  2. ,
    via GitHub by ritchieGitHub

    Set larger socket timeout (or 0 to set no timeout).

Solutions on the web

via runawfe by erickv
, 1 year ago
Software caused connection abort: socket write error
via YouTrack by Unknown author, 2 years ago
via Pentaho BI Platform Tracking by Ruth Cook, 1 year ago
via Stack Overflow by adis
, 2 years ago
java.net.SocketException: Software caused connection abort: socket write error  	at java.net.SocketOutputStream.socketWrite0(Native Method)	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)	at java.net.SocketOutputStream.write(SocketOutputStream.java:136)	at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:737)	at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434)	at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349)	at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:761)	at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:126)	at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:570)	at org.apache.coyote.Response.doWrite(Response.java:560)	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:353)