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 Oracle Community by 4790, 1 year ago
via Oracle Community by 843836, 5 months ago
via zeroc.com by Unknown author, 1 year ago
via grokbase.com by Unknown author, 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 org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:457)	at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:654)	at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:435)	at org.apache.coyote.Response.action(Response.java:226)	at org.apache.coyote.Response.finish(Response.java:348)	at org.apache.coyote.tomcat5.OutputBuffer.close(OutputBuffer.java:328)	at org.apache.coyote.tomcat5.CoyoteResponse.finishResponse(CoyoteResponse.java:497)	at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:213)	at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309)	at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387)	at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673)	at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:615)	at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786)	at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:677)	at java.lang.Thread.run(Thread.java:536)