Broken Pipe是什么意思?

Question

这是具体的报错信息,大家看看啊
WARNING: Exception Processing ErrorPage[errorCode=404, location=/index.asp]
ClientAbortException:  java.net.SocketException: Broken pipe
        at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:366)
        at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433)
        at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:348)
        at org.apache.tomcat.util.buf.IntermediateOutputStream.write(C2BConverter.java:235)
        at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
        at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395)
        at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136)
        at java.io.OutputStreamWriter.write(OutputStreamWriter.java:191)
        at org.apache.tomcat.util.buf.WriteConvertor.write(C2BConverter.java:189)
        at org.apache.tomcat.util.buf.C2BConverter.convert(C2BConverter.java:80)
        at org.apache.catalina.connector.OutputBuffer.realWriteChars(OutputBuffer.java:535)
        at org.apache.tomcat.util.buf.CharChunk.flushBuffer(CharChunk.java:439)
        at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:310)
        at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:293)
        at org.apache.catalina.connector.Response.flushBuffer(Response.java:537)
        at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:286)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
        at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199)
        at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
        at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
        at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:684)
        at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:876)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
        at java.lang.Thread.run(Thread.java:595)
Caused by: 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:518)
        at org.apache.jk.common.JkInputStream.doWrite(JkInputStream.java:147)
        at org.apache.coyote.Response.doWrite(Response.java:559)
        at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:361)

Answer 1

我找的一些资料，仅供参考
linux下webloigc经常出现broken pipe，socket....connection reset错误...... 
       linux下webloigc经常出现broken pipe，socket....connection reset错误.        有有可能是linux的线程机制会产生JVM出错的问题，特别是在连接高峰期间经常出现这样的问题，tomcat在linux下也出现类似情况。        解决办法是在环境变量中设置： _JAVA_SR_SIGNUM = 12 基本就可以解决。 sun的解释： 
－－posted by: cooper 
Below is a clipping from Sun on working around JVM crashes under high 
thread counts in the JVM 1.3 for Linux On Linux, use a larger signal number for hotspot thread 
suspension/resumption handler. The signal number being used is 
specified by environment variable _JAVA_SR_SIGNUM. Setting it to a 
number larger than SIGSEGV (11) will solve the problem. A good number 
to use is 12, which is SIGUSR2. Using signal 16 to work around the 
problem might have potential problems. So on tcsh, "setenv 
_JAVA_SR_SIGNUM 12" can solve the problem.如果解决了，告诉我一下

Answer 2

_JAVA_SR_SIGNUM = 12 绝对不能解决我已经试验过了。注意必须是“_JAVA_SR_SIGNUM=12”等号两边必须没有空格，等号是半角网上几乎所有答案都是错害人不浅