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.java:537
)
at
org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(CoyoteResponseFac
ade.java:238)
at
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:303
)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:147
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
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:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.ja
va:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
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]
