I think a lot of people have lots of these entries. :) Here's my idea: What it means is that the client (your browser) has closed the tcp/ip connection between itself and Tomcat, before Tomcat thinks it is done sending data.
Since the images and pages seem to be 100% complete (because you don't mention that you are experiencing any actual page load problems), one could wonder whether or not Tomcat is correct, but putting that aside... the problem is not Tomcat related, so much as it is connection related. The 'solution' is to simply disable this message. In Tomcat 3.2.x, go to <TOMCAT_HOME>/conf/server.xml and modify the following: code: ----------------------------------------------------- <Logger name="tc_log" verbosityLevel = "INFORMATION" ----------------------------------------------------- Change "INFORMATION" to "WARNING", and that particular message should no longer appear. You will still get all the error stack traces, but none of the 'information' messages. I haven't found how to set this in Tomcat 4.x. Can someone else help us out on that one? > -----Original Message----- > From: Jiang Chen [mailto:[EMAIL PROTECTED] > Sent: Friday, September 05, 2003 11:35 PM > To: Tomcat Users List > Subject: Connection reset by peer: socket write error in tomcat log > > > Hi; > > I have quite a lot following exception in the tomcat log: > > ErrorDispatcherValve[localhost]: Exception Processing > ErrorPage[errorCode=404, location=/pages/error.jsp] > java.net.SocketException: Connection reset by peer: socket write error > at java.net.SocketOutputStream.socketWrite(Native Method) > at java.net.SocketOutputStream.write(SocketOutputStream.java:91) > at > org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutp > utBuffer.doWri > te(InternalOutputBuffer.java:668) > at > org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(C > hunkedOutputFi > lter.java:171) > at > org.apache.coyote.http11.InternalOutputBuffer.doWrite(Internal > OutputBuffer.j > ava:523) > at org.apache.coyote.Response.doWrite(Response.java:524) > at > org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBu > ffer.java:384) > at > org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) > at > org.apache.coyote.tomcat4.OutputBuffer.flush(OutputBuffer.java:345) > at > org.apache.coyote.tomcat4.CoyoteResponse.flushBuffer(CoyoteRes > ponse.java:555 > ) > at > org.apache.coyote.tomcat4.CoyoteResponseFacade.flushBuffer(Coy > oteResponseFac > ade.java:227) > at > org.apache.catalina.valves.ErrorDispatcherValve.status(ErrorDi > spatcherValve. > java:307) > at > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDi > spatcherValve. > java:180) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invok > eNext(StandardPipeline.java:641) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport > Valve.java:172 > ) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invok > eNext(StandardPipeline.java:641) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipel > ine.java:480) > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEn > gineValve.java > :174) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invok > eNext(StandardPipeline.java:643) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipel > ine.java:480) > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > at > org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter. > java:223) > at > org.apache.coyote.http11.Http11Processor.process(Http11Process > or.java:432) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandle > r.processConne > ction(Http11Protocol.java:386) > at > org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoi > nt.java:534) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( > ThreadPool.jav > a:530) > at java.lang.Thread.run(Thread.java:479) > > I am using Tomcat 4.1.18 and Structs 1.0, running at w2k box. > > Does anyone know what cause it, and how to fix it? > > Thanks a lot > > Jiang > > > --------------------------------------------------------------------- > 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]
