java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@5fc6a274:Socket[addr=/10.161.169.241,port=41112,localport=7003] - idle timeout: '30000' ms, socket timeout: '5000' ms', in the configured timeout period of '60' secs

Oracle Community | Nishithaa | 12 months ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Unable to access weblogic console after clone

    Oracle Community | 12 months ago | Nishithaa
    java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@5fc6a274:Socket[addr=/10.161.169.241,port=41112,localport=7003] - idle timeout: '30000' ms, socket timeout: '5000' ms', in the configured timeout period of '60' secs
  2. 0

    timeout error on weblogic cluster

    Oracle Community | 3 years ago | user11163933
    java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@4bd7f3dd:Socket[addr=/10.0.0.32,port=55179,localport=7002] - idle timeout: '30000' ms, socket timeout: '5000' ms', in the configured timeout period of '60' secs
  3. 0

    timeout error on weblogic cluster

    Stack Overflow | 3 years ago | hellzone
    java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@4bd7f3dd:Socket[addr=/10.0.0.32,port=55179,localport=7002] - idle timeout: '30000' ms, socket timeout: '5000' ms', in the configured timeout period of '60' secs
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Users getting timed out in WL 9.2

    Oracle Community | 9 years ago | Thaya-Oracle
    java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@5b669c:Socket[addr=/10.88.10.56,port=22327,localport=7001] - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
  6. 0

    BEA-101083 and BEA-000337

    Oracle Community | 9 years ago | Thaya-Oracle
    java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@5c014f:Socket[addr=/172.19.18.35,port=3736,localport=80] - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.io.IOException

      A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@5fc6a274:Socket[addr=/10.161.169.241,port=41112,localport=7003] - idle timeout: '30000' ms, socket timeout: '5000' ms', in the configured timeout period of '60' secs

      at weblogic.socket.SocketMuxer$TimerListenerImpl.timerExpired()
    2. weblogic.socket
      SocketMuxer$TimerListenerImpl.timerExpired
      1. weblogic.socket.SocketMuxer$TimerListenerImpl.timerExpired(SocketMuxer.java:1078)
      1 frame
    3. weblogic.timers.internal
      TimerImpl.run
      1. weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
      1 frame
    4. weblogic.work
      ExecuteThread.run
      1. weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
      2. weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
      3. weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
      3 frames