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.com by Unknown author

    Upgrade your docker-selenium

  2. ,
    via github.com by Unknown author

    Client closed the websocket connection (safe to ignore)

Solutions on the web

via Atlassian JIRA by Brendan Smith, 1 year ago
Broken pipe
via Oracle Community by 843838, 4 months ago
via Oracle Community by 843838, 4 months ago
via xml-xindice-users by Todd Byrne, 1 year ago
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 weblogic.servlet.internal.ChunkUtils.writeChunkTransfer(ChunkUtils.java:247)	at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:223)	at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:298)	at weblogic.servlet.internal.ChunkOutput.checkForFlush(ChunkOutput.java:373)	at weblogic.servlet.internal.ChunkOutput.write(ChunkOutput.java:243)	at weblogic.servlet.internal.ChunkOutputWrapper.write(ChunkOutputWrapper.java:113)	at weblogic.servlet.internal.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:184)	at weblogic.servlet.internal.WLOutputStreamWriter.write(WLOutputStreamWriter.java:111)	at weblogic.servlet.internal.WLOutputStreamWriter.write(WLOutputStreamWriter.java:126)	at weblogic.servlet.internal.DelegateChunkWriter.print(DelegateChunkWriter.java:99)