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 Coderanch by srinivas kumarr, 1 year ago
Broken pipe
via coderanch.com by Unknown author, 1 year ago
via coderanch.com by Unknown author, 1 year ago
via xml-xindice-users by Todd Byrne, 2 years 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 com.certicom.io.OutputSSLIOStream.write(Unknown Source)	at com.certicom.tls.record.WriteHandler.flushOutput(Unknown Source)