IBM Support

java.net.SocketException: Write failed: Broken pipe exception' in the MCS application logs *|* -DC0547B87EE5FDF2852579180

Question & Answer


Question

java.net.SocketException: Write failed: Broken pipe exception' in the MCS application logs *|* -DC0547B87EE5FDF28525791800061D83- *|*

Answer

Technote (troubleshooting)


Problem(Abstract)

'java.net.SocketException: Write failed: Broken pipe exception' in the MCS application logs

Symptom

Example Scenario: User hits the update button and closes the browser while the application is calculating. The exception is thrown because the browser is missing when it is time to display the results.

This exception is seen in the Multi Channel Selling (MCS) application logs intermittently. 'Broken pipe' errors usually occur when the browser is closed before the request can be completed. They are harmless. There are various reasons but the most common being a browser session being closed while the request is still processing.

Error Message

2009.12.10 15:38:05:853 Env/[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)':INFO:UserPropertyMgr Invalid user property for storefront 99 property userCartMode
java.net.SocketException: Write failed: Broken pipe
at
jrockit.net.SocketNativeIO.writeBytesPinned(Native Method)
at
jrockit.net.SocketNativeIO.socketWrite(SocketNativeIO.java:45)
at
java.net.SocketOutputStream.socketWrite0(SocketOutputStream.java)
at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at
java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at weblogic.servlet.internal.ChunkOutput.writeChunkTransfer(ChunkOutput.java:525)
at weblogic.servlet.internal.ChunkOutput.writeChunks(ChunkOutput.java:504)
at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:382)
at weblogic.servlet.internal.CharsetChunkOutput.flush(CharsetChunkOutput.java:249)
at weblogic.servlet.internal.ChunkOutputWrapper.flush(ChunkOutputWrapper.java:164)
at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:113)
at weblogic.servlet.internal.WLOutputStreamWriter.flush(WLOutputStreamWriter.java:160)
at weblogic.servlet.internal.DelegateChunkWriter.flush(DelegateChunkWriter.java:132)
at weblogic.servlet.internal.ChunkOutputWrapper.flush(ChunkOutputWrapper.java:164)
at weblogic.servlet.jsp.JspWriterImpl.flush(JspWriterImpl.java:73)
at jsp_servlet._web_45_inf._web._en._gb._enterprisemgr._home.__homedata._jspService(__homedata.java:1290)
at
com.comergent.dcm.core.BaseJSP.service(BaseJSP.java:61)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at
com.comergent.dcm.core.filters.ComergentFilter.doFilter(ComergentFilter.java:50)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at
com.comergent.dcm.core.filters.ComergentFilter.doFilter(ComergentFilter.java:50)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at
com.comergent.dcm.core.filters.ComergentFilter.doFilter(ComergentFilter.java:50)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:526)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:261)
at
com.comergent.dcm.core.ComergentDispatcher.forward(ComergentDispatcher.java:70)
at
com.comergent.dcm.caf.controller.ForwardController.callJSP(ForwardController.java:76)
2009.12.10 15:38:05:855 Env/[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)':INFO:ComergentDispatcher < JSP.forward /WEB-INF/web/en/GB/enterpriseMgr/home/HomeData.jsp alloc=0</span></span></p> <p>


Resolving the problem

The errors in the logs do not have any effect on the processes in the application. The error only appears when the browser is closed by the user. It is not a true error hence there is no resolution.

Historical Number

NFX7993

Product Alias/Synonym

Function Area


application server

Escalation ID


123222

Severity


Normal

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SS73G6","label":"Sterling Total Payments for Financial Services"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
13 October 2021

UID

ibm10770773