Good input, but the site is not being accessed by anyone but me right now and I sure did NOT cancel the page load. So, this is being caused by something else...
Michael ----- Original Message ----- From: "Shapira, Yoav" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Wednesday, July 28, 2004 5:50 AM Subject: RE: Broken pipe exception with every request! Hi, As the error message hints, a common cause for this exception is the client closing the browser while you're generating the page. People do that often when they run into error pages, e.g. as soon as they see the 404 header. I don't know what the rest of your 404.jsp does, but you should try to make it a very simple and quick page (preferably a static one). Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: Michael Mehrle [mailto:[EMAIL PROTECTED] >Sent: Tuesday, July 27, 2004 4:35 PM >To: Tomcat Users List >Subject: Broken pipe exception with every request! > >I got up this morning and noticed that my production server was down. So, I >checked tomcat's log and found a whole bunch of these: > >2004-07-27 08:09:31 [EMAIL PROTECTED]: >Exception Processing ErrorPage[errorCo >de=404, location=/404.jsp] >ClientAbortException: java.net.SocketException: Broken pipe > at >org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:331) > at >org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:297) > at >org.apache.coyote.tomcat5.CoyoteResponse.flushBuffer(CoyoteResponse.jav a:53 >7 >) > at >org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(CoyoteRespon seFa >c >ade.java:238) > at >org.apache.catalina.core.StandardHostValve.status(StandardHostValve.jav a:30 >3 >) > at >org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.jav a:14 >7 >) > at >org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC onte >x >t.java:104) > at >org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.jav a:11 >7 >) > at >org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC onte >x >t.java:102) > at >org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 520) > at >org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve .jav >a >:109) > at >org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC onte >x >t.java:104) > at >org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 520) > at >org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) > at >org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) > at >org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:7 99) > at >org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process Conn >e >ction(Http11Protocol.ja >va:705) > at >org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:5 77) > at >org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.ja >v >a:683) > at java.lang.Thread.run(Thread.java:534) > >Tailing the log once I restarted tomcat revealed that this error is being >thrown with EVERY REQUEST - no matter what page! Something's very fishy >here... BTW - I have the same application running on my staging server and >do not get these error messages. > >Also, the server is pretty slow frankly and I wonder if that's related >somehow. > >Michael > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
