为什么我收到“错误提交响应 java.io.IOException:sun.nio.ch.FileDispatcher.write0(本机方法)处的管道损坏”? 与 SSL
当我将页面从 http 重定向到 https 时,我遇到了此异常。 奇怪的是,我可以在前 10 到 20 个请求中访问 https。 但后续请求我遇到了这个损坏的管道问题
,下面是完整的异常
Error commiting responsejava.io.IOException: Broken pipeline at sun.nio.ch.FileDispatcher.write0(Native Method) at sun.nio.ch.SocketDispatcher.write( SocketDispatcher.java:29) 在 sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104) 在 sun.nio.ch.IOUtil.write(IOUtil.java:75) 在 sun.nio.ch.SocketChannelImpl.write (SocketChannelImpl.java:302) 在 com.sun.enterprise.server.ss.ASOutputStream.write(ASOutputStream.java:120) 在 com.sun.net.ssl.internal.ssl.OutputRecord.writeBuffer(OutputRecord.java:283) )在 com.sun.net.ssl.internal.ssl.OutputRecord.write(OutputRecord.java:272) 在 com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:666) 在 com. sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59) 在 org.apache.coyote.http11.InternalOutputBuffer.commit(InternalOutputBuffer.java:602) 在 com.sun.enterprise.web.connector。 grizzly.ProcessorTask.action(ProcessorTask.java:721) 在 org.apache.coyote.Response.action(Response.java:188) 在 org.apache.coyote.Response.sendHeaders(Response.java:380) 在 org.apache .coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:357) 在 org.apache.coyote.tomcat5.OutputBuffer.close(OutputBuffer.java:318) 在 org.apache.coyote.tomcat5.CoyoteResponse.finishResponse(CoyoteResponse.java :528)在 org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:192)在 com.sun.enterprise.web.connector.grizzly.ProcessorTask.doProcess(ProcessorTask.java:604)在 com.sun。 enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:475) 位于 com.sun.enterprise.web.connector.grizzly.ProcessorTask.doTask(ProcessorTask.java:426) 位于 com.sun.enterprise.web。连接器.grizzly.TaskBase.run(TaskBase.java:281) 在 com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:83
I encounter this exception when i do a page redirect from http to https. And the strange thing is that i can access https in the first 10 to 20 requests. But subsequent requests that i encounter this broken pipe issue
Below is the full exception
Error commiting responsejava.io.IOException: Broken pipe at sun.nio.ch.FileDispatcher.write0(Native Method) at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29) at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104) at sun.nio.ch.IOUtil.write(IOUtil.java:75) at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:302) at com.sun.enterprise.server.ss.ASOutputStream.write(ASOutputStream.java:120) at com.sun.net.ssl.internal.ssl.OutputRecord.writeBuffer(OutputRecord.java:283) at com.sun.net.ssl.internal.ssl.OutputRecord.write(OutputRecord.java:272) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:666) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59) at org.apache.coyote.http11.InternalOutputBuffer.commit(InternalOutputBuffer.java:602) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.action(ProcessorTask.java:721) at org.apache.coyote.Response.action(Response.java:188) at org.apache.coyote.Response.sendHeaders(Response.java:380) at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:357) at org.apache.coyote.tomcat5.OutputBuffer.close(OutputBuffer.java:318) at org.apache.coyote.tomcat5.CoyoteResponse.finishResponse(CoyoteResponse.java:528) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:192) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doProcess(ProcessorTask.java:604) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:475) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doTask(ProcessorTask.java:426) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:281) at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:83
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我通过增加 JVM 可用的 RAM 解决了类似的问题,例如:
I have resolved a similar issue by increasing the RAM available to the JVM, e.g: