Follow Us on Twitter

“broken pipe” errors in the OSB logs

by Patrick Sinke on December 3, 2013 · 0 comments

At a customer’s site, we experienced messages being delivered twice; one on every node of the OSB cluster.

This is what we found in the logs:

<Error> <WliSbTransports> <BEA-381304> <Exception in HttpTransportServlet.service: java.io.IOException: java.net.SocketException: Broken pipe
 java.io.IOException: java.net.SocketException: Broken pipe at com.bea.wli.sb.transports.http.ResourceRequestProcessor.securedInvoke(ResourceRequestProcessor.java:95)

The solution is straightforward: disable the setting “Use Chunked Streaming Mode” on the business service. It’s part of the HTTP Transport Configuration in the Configuration Details.

Note that the Oracle documentation discourages use of this settings in specific cases, so check if these apply to your configuration:

Note: Do not use chunked streaming with if you use the Follow HTTP Redirects option. Redirection and authentication cannot be handled automatically in chunked mode.”

 The reason the message is delivered twice, is probably because the first transaction fails and is rolled back, but the message is already sent.

"broken pipe" errors in the OSB logs, 3.0 out of 5 based on 1 rating
Ratings:
VN:F [1.9.22_1171]
Rating: 3.0/5 (1 vote cast)

{ 0 comments… add one now }

Leave a Comment

 

Previous post:

Next post:

About Whitehorses
Company profile
Services
Technology

Whitehorses website

Home page
Whitebooks
Jobs

Follow us
Blog post RSS
Comment RSS
Twitter