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 JBoss Issue Tracker by Andre Pankraz, 1 year ago
via ICEsoft JIRA Issue Tracker by Carmen Cristurean, 1 year ago
via Stack Overflow by Rosswerks
, 2 years ago
via Stack Overflow by Steve Waters
, 7 months ago
via Stack Overflow by semudu
, 1 year ago Broken pipe
via Stack Overflow by Alisson Vieira
, 2 years ago
java.lang.RuntimeException: Broken pipe at io.undertow.servlet.spec.HttpServletResponseImpl.responseDone( at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest( at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest( at io.undertow.servlet.handlers.ServletInitialHandler.access$000( at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest( at io.undertow.server.Connectors.executeRootHandler( at io.undertow.server.HttpServerExchange$ at java.util.concurrent.ThreadPoolExecutor.runWorker([rt.jar:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor$[rt.jar:1.7.0_45] at[rt.jar:1.7.0_45]Caused by: Broken pipe at Method)[rt.jar:1.7.0_45] at[rt.jar:1.7.0_45] at[rt.jar:1.7.0_45] at[rt.jar:1.7.0_45] at[rt.jar:1.7.0_45] at org.xnio.nio.NioSocketConduit.write([xnio-nio-3.1.0.CR7.jar:3.1.0.CR7] at io.undertow.server.protocol.http.HttpResponseConduit.write(