管道中断错误后的Tomcat servlet映射错误

我们已经在Tomcat版本7.0.23中实现了Servlet3.0AsyncContext

它使用OpenJDK版本1.6.0\u 24,64位服务器在

RHEL6.1中运行

该应用程序在大部分情况下运行良好。
当网络中出现一些干扰时，来自服务器的更新无法到达客户端，因为存在“
ClientAbortException:java.net.SocketException:breaked 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那边的一只虫子

首先，我将尝试更新到ApacheTomcat 7.0。64

其次，我会尝试更新到Java6u45
我们的服务器端也有类似的问题。事实证明，我们发送的响应数据集在过滤器级别被阻塞，因为数据非常庞大，在这个级别爆炸了

@Component
public class TrackingFilter implements TraceRepository, Filter {
/**
* Few other business relarted code
*
byte[] bytes = pw.toByteArray();
response.getOutputStream().write(bytes);
}

嗨，你找到解决办法或原因了吗？