gpt4 book ai didi

Broken pipe 错误后 Tomcat servlet 映射错误

转载 作者:行者123 更新时间:2023-11-28 21:46:47 26 4
gpt4 key购买 nike

我们在 Tomcat Version:7.0.23 中实现了 Servlet 3.0 AsyncContext。

它在 RHEL 6.1 中运行,使用 OpenJDK version 1.6.0_24,64-bit 服务器

该应用程序在大多数情况下运行良好。当网络出现一些干扰时,来自服务器的更新无法到达客户端,因为存在“ClientAbortException: java.net.SocketException: Broken pipe”异常。被捕获并被忽略。

这发生在行中,

asyncContext.getResponse().getWriter().println(updateStr);

在此之后,Tomcat 变得疯狂并将 URL 路由到意外的 servlet。例如,将/query 映射到名为 SessionManager 的 servlet,URL mysite.com/index.html 被路由到 SessionManager servlet。只能重启tomcat解决问题。

关于为什么会发生这种情况以及如何解决这个问题的任何指示?

只是为了添加更多数据,以下是异常的堆栈跟踪。

ClientAbortException:  java.net.SocketException: Broken pipe
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:346)
at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:306)
at org.apache.catalina.connector.Response.flushBuffer(Response.java:568)
at org.apache.catalina.connector.ResponseFacade.flushBuffer(ResponseFacade.java:307)
at com.management.TestHandler$TestInfo.statusUpdate(TestHandler.java:638)
at com.chakra.ipbtt.TestObject.publish(TestObject.java:1626)
at com.chakra.ipbtt.TestObject.handlePublish(TestObject.java:1421)
at com.chakra.ipbtt.TestObject.executeCommand(TestObject.java:1371)
at com.chakra.ipbtt.TestObject.executeCommand(TestObject.java:1388)
at com.chakra.ipbtt.TestObject.executeCommand(TestObject.java:1388)
at com.chakra.ipbtt.TestObject.executeCommand(TestObject.java:1388)
at com.chakra.ipbtt.TestObject.executeCommand(TestObject.java:1388)
at com.chakra.ipbtt.TestObject.executeCommand(TestObject.java:1388)
at com.chakra.ipbtt.TestObject.executeTest(TestObject.java:1791)
at com.management.TestHandler.executeTest(TestHandler.java:420)
at com.management.TestHandler.handleNewTest(TestHandler.java:222)
at com.management.TestMgr.processRequest(TestMgr.java:71)
at com.management.TestMgr.doPost(TestMgr.java:105)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:690)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:477)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:402)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:329)
at com.management.SessionMgr.processRequest(SessionMgr.java:131)
at com.management.SessionMgr.doPost(SessionMgr.java:164)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at com.management.SessionsFilter.doFilter(SessionsFilter.java:127)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)

Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:215)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:462)
at org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:119)
at org.apache.coyote.http11.AbstractHttp11Processor.action(AbstractHttp11Processor.java:789)
at org.apache.coyote.Response.action(Response.java:174)
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:341)
... 48 more`

最佳答案

这听起来像是 Tomcat 方面的一个错误。

首先,我会尝试更新到 Apache Tomcat 7.0.64

其次,我会尝试更新到 Java 6u45

关于Broken pipe 错误后 Tomcat servlet 映射错误,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/11555029/

26 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com