java.io.IOException

A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@a6be6e:Socket[addr=/10.188.10.156,port=15371,localport=7001] - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web21490

  • via Oracle Community by Thaya-Oracle, 1 year ago
    A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@a6be6e:Socket[addr=/10.188.10.156,port=15371,localport=7001] - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
  • via Oracle Community by Thaya-Oracle, 11 months ago
    A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@a6be6e:Socket[addr=/10.188.10.156,port=15371,localport=7001] - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
  • via Coderanch by Thaya Thava, 8 months ago
    A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1887305:Socket[addr=/10.88.10.56,port=28982,localport=7001] - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
  • Stack trace

    • java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@a6be6e:Socket[addr=/10.188.10.156,port=15371,localport=7001] - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs at weblogic.socket.SocketMuxer$TimerListenerImpl.timerExpired(SocketMuxer.java:947) at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265) at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.