"java.net.SocketException: Broken pipe" was shown in JBoss or Tomcat log?

Solution Verified - Updated -

Issue

  • The following exception was shown in JBoss server.log or Tomcat catalina.out. What causes this?

    WARN  [MsgContext] Error sending end packet
    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:531)
           at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:112)
           at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
           at org.apache.coyote.Response.action(Response.java:182)
           at org.apache.coyote.Response.finish(Response.java:304)
           at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:204)
           at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
           at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
           at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
           at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
           at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
           at java.lang.Thread.run(Thread.java:595)
    WARN  [ChannelSocket] processCallbacks status 2
    
  • JBoss EAP hung with above error in logs.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 4.x
    • 5.x
  • Tomcat
    • 5.5
    • 6.0
  • Apache httpd
    • mod_jk
    • mod_proxy

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In