2012-07-19 87 views
6

我們已經在Tomcat版本7.0.23中實現了Servlet 3.0 AsyncContext。斷開管道錯誤後Tomcat servlet映射錯誤

它在RHEL 6.1 using 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` 
+1

嗨,你找到任何解決方案或原因? – 2015-03-12 08:34:12

回答

0

這聽起來像是Tomcat側面的一個bug。

首先,我會嘗試更新到Apache Tomcat 7.0。 。

其次,我會嘗試更新到Java 6u 。