لم تعُد "مجموعات Google" تتيح المشاركات أو الاشتراكات الجديدة من Usenet. وسيبقى بالإمكان عرض المحتوى السابق.

suppress "java.io.IOException: Broken pipe"

مرّة مشاهدة واحدة
التخطي إلى أول رسالة غير مقروءة

dan

غير مقروءة،
29‏/03‏/2004، 11:03:17 ص29‏/3‏/2004
إلى
Dear All,

Our log files are becoming increasingly difficult to read due to
exceptions thrown such as the following:

[3/25/04 10:35:30:493 CET] cf510 SystemOut U [Thu Mar 25
10:35:30 CET] Error: CoreMedia Generator: Broken pipe
java.io.IOException: Broken pipe
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java:91)
at com.ibm.ws.io.Stream.write(Stream.java:26)
at com.ibm.ws.io.WriteStream.flushMyBuf(WriteStream.java:131)
at com.ibm.ws.io.WriteStream.flush(WriteStream.java:123)
at com.ibm.ws.http.ResponseStream.flush(ResponseStream.java:326)
at com.ibm.ws.io.WriteStream.flush(WriteStream.java:125)
at com.ibm.servlet.engine.http11.HttpConnection.flush(HttpConnection.java:383)
at com.ibm.servlet.engine.srp.SRPConnection.flush(SRPConnection.java:242)
at com.ibm.servlet.engine.srt.SRTOutputStream.flush(SRTOutputStream.java:41)
at com.ibm.servlet.engine.srt.BufferedServletOutputStream.flushBytes(BufferedServletOutputStream.java:340)
at com.ibm.servlet.engine.srt.BufferedServletOutputStream.write(BufferedServletOutputStream.java:293)
at hox.util.InputOutput.start(InputOutput.java:62)
at hox.corem.servlets.Page.copyContentsTo(Page.java:153)
at hox.corem.servlets.GeneratorServlet.service(GeneratorServlet.java:500)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:827)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:167)
at com.ibm.servlet.engine.webapp.ServicingServletState.service(StrictLifecycleServlet.java:317)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:110)
at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:1012)
at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:913)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:721)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:374)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:118)
at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:239)
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:151)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:317)
at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:477)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:351)
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:144)

We are not interested in this error message, as we are aware that this
is being caused by users prematurely abandoning the page.

Could anybody tell me how this message can be supressed?

We have found many questions with the same problem, but we are still
looking for answers.

Your help would be greatly appreciated.

Best regards

Dan Bloch
Web Developer

0 رسالة جديدة