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 Rudy Rusli, 1 year ago
via Apache Bugzilla by support, 1 year ago
via Apache Bugzilla by paul.hettl, 9 months ago
via Google Groups by carlo, 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 org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:537)	at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:127)	at org.apache.jk.core.MsgContext.action(MsgContext.java:302)	at org.apache.coyote.Response.action(Response.java:221)	at org.apache.coyote.Response.finish(Response.java:346)	at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:205)	at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)	at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773)	at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703)	at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:895)	at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666)	at java.lang.Thread.run(Thread.java:619)