My Oracle Support Banner

SOA 11.1.1.7: Getting unexpected read timeouts when calling Service Bus web services from SOA (Doc ID 2170515.1)

Last updated on JANUARY 14, 2018

Applies to:

Oracle SOA Suite - Version 11.1.1.7.7 and later
Information in this document applies to any platform.

Symptoms


When calling a Service Bus web service, random read timeouts are occuring along with the following:

Jul 28, 2016 10:30:58 AM GMT-03:00> java.io.IOException: SocketMuxer detected socket closure while waiting for a response
at weblogic.net.http.SocketClosedNotification.(SocketClosedNotification.java:10)
at weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse.handleError(AsyncResponseHandler.java:396)
at weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse.hasException(AsyncResponseHandler.java:504)
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:827)
at weblogic.socket.SocketMuxer.deliverHasException(SocketMuxer.java:767)
Truncated. see log file for complete stacktrace


java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at weblogic.socket.JSSEFilterImpl.writeToNetwork(JSSEFilterImpl.java:681)
at weblogic.socket.JSSEFilterImpl.wrapAndWrite(JSSEFilterImpl.java:643)
Truncated. see log file for complete stacktrace
>



Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.