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. ,

    The socket has shut down its end of the socket before communication was complete. About half of those were because the program communicating on that socket had terminated. Check whether the application is still up and communicating via the socket.

Solutions on the web

via JIRA by Michael Smith, 1 year ago
null
via JIRA by Michael Smith, 1 year ago
null
via Google Groups by Mariano Mirabelli, 1 year ago
java.io.IOException: Broken pipe	at sun.nio.ch.FileDispatcherImpl.write0(Native Method)	at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)	at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)	at sun.nio.ch.IOUtil.write(IOUtil.java:65)	at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:492)	at org.eclipse.jetty.io.ChannelEndPoint.flush(ChannelEndPoint.java:170)	at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.flush(SslConnection.java:793)	at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:408)	at org.eclipse.jetty.io.WriteFlusher.completeWrite(WriteFlusher.java:364)	at org.eclipse.jetty.io.ssl.SslConnection$1.run(SslConnection.java:97)	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)	at java.lang.Thread.run(Thread.java:745)