OAM Log Error: BEA-101083 - Connection Failure - A Complete Message Could Not Be Read On Socket

(Doc ID 1500019.1)

Last updated on AUGUST 08, 2017

Applies to:

Oracle Access Manager - Version 11.1.1.3.0 to 11.1.2.0.0 [Release 11g]
Information in this document applies to any platform.

Goal

Getting below error in nohup.out in our Prod environment,

java.io.IOException: A complete message could not be read on socket: 'SSLFilterImpl[weblogic.servlet.internal.MuxableSocketHTTP@6ccec324:Socket[addr=/10.16.37.119,port=62981,localport=10110]com.certicom.tls.interfaceimpl.TLSConnectionImpl@70e4ca66 - idle timeout: '60000' ms, socket timeout: '25000' ms]', in the configured timeout period of '60' secs
at weblogic.socket.SocketMuxer$TimerListenerImpl.timerExpired(SocketMuxer.java:1070)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

This message is not the result of an actual problem that is occuring. Is it something to be concerned with?
 

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms