My Oracle Support Banner

Timeout and Frequent BEA-381304 Errors Due to Abnormal Socket Termination within the Socket Muxer Layer (Doc ID 981178.1)

Last updated on JULY 31, 2018

Applies to:

Oracle Service Bus - Version 2.6 to 2.6.1RP [Release Aqualogic Service Bus]
Information in this document applies to any platform.
***Checked for relevance on 05-Mar-2014***


Timeout and frequent BEA-381304 errors due to abnormal socket termination within the socket muxer layer are happening in your system.
This problem happens only with HTTPS. When Keep-Alive is disabled on WebLogic Server and the browser sends a POST request to a servlet, in case the servlet does not implement getParameter method, WLS sends a RST packet while sending a response.

ALSB is unable to gracefully handle RST packages sent by a backend server. Backend WebServices deployed  on a Backend server could be anything for example JBOSS or AXIS.
In the log file, the following exception trace will be available:
<BEA-381304> <Exception in SocketMuxer detected socket closure while waiting for a response SocketMuxer detected socket closure while waiting for a response 
at weblogic.socket.SSLFilter.endOfStream(
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(
at weblogic.socket.SocketMuxer.deliverEndOfStream(
at weblogic.socket.SSLFilter.isMessageComplete(
at weblogic.socket.SocketMuxer.readReadySocketOnce(
at weblogic.socket.SocketMuxer.readReadySocket(
at weblogic.socket.EPollSocketMuxer.dataReceived(
at weblogic.socket.EPollSocketMuxer.processSockets(
at weblogic.socket.SocketReaderRequest.execute(
at weblogic.kernel.ExecuteThread.execute(


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

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