java.net.SocketException

Broken pipe

Samebug tips13

Upgrade your docker-selenium

Client closed the websocket connection (safe to ignore)

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web1572

  • via Oracle Community by 3004, 1 year ago
    Broken pipe: Broken pipe
  • via GitHub by fromgate
    , 1 year ago
    Broken pipe
  • Stack trace

    • java.net.SocketException: Broken pipe at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:362) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:437) at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:391) at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:374) at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:93) at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:86) at org.icepush.http.standard.FixedSizeContentHandler.respond(FixedSizeContentHandler.java:51) at org.icepush.http.standard.FixedXMLContentHandler.respond(FixedXMLContentHandler.java:37) at org.icepush.servlet.ServletRequestResponse.respondWith(ServletRequestResponse.java:206) at org.icepush.servlet.ThreadBlockingAdaptingServlet$ThreadBlockingRequestResponse.respondWith(ThreadBlockingAdaptingServlet.java:67) at org.icepush.BlockingConnectionServer.respondIfPendingRequest(BlockingConnectionServer.java:196) Caused by: java.net.SocketException: Broken pipe 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.ajp.AjpProcessor$SocketOutputBuffer.doWrite(AjpProcessor.java:629) at org.apache.coyote.Response.doWrite(Response.java:533) at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:357) ... 11 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 2 years ago
    Unknown user
    Once, 6 months ago
    Unknown user
    Once, 11 months ago
    Unknown user
    Once, 1 year ago
    233 more bugmates