java.io.IOException: A complete message could not be read on socket: 'weblogic.rjvm.t3.T3JVMConnection@11a5fd0', in the configured timeout period of '60' secs

Oracle Community | 666705 | 1 decade ago
  1. 0

    java.io.IOException: A complete message could not be read on socket

    Oracle Community | 1 decade ago | 666705
    java.io.IOException: A complete message could not be read on socket: 'weblogic.rjvm.t3.T3JVMConnection@11a5fd0', in the configured timeout period of '60' secs
  2. 0

    BEA-101083 : Connection Failure Error?

    Oracle Community | 1 decade ago | 666705
    java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@13704c7 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
  3. 0

    Weblogic 8.1 remote debugging problem

    Oracle Community | 1 decade ago | 3004
    java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1871db 1 - idle timeout: '60000' 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

    <BEA-101083> <Connection failure.

    Oracle Community | 1 decade ago | 3004
    java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1c94ff 3 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
  6. 0

    <BEA-101083> <Connection failure

    Oracle Community | 1 decade ago | 3004
    java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1c94ff 3 - 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.rjvm.t3.T3JVMConnection@11a5fd0', in the configured timeout period of '60' secs

      at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger()
    2. weblogic.socket
      SocketMuxer$TimeoutTrigger.trigger
      1. weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(SocketMuxer.java:776)
      1 frame
    3. weblogic.time.common
      ScheduledTrigger.run
      1. weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
      1 frame
    4. weblogic.security.acl
      AuthenticatedSubject.doAs
      1. weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
      1 frame
    5. weblogic.security.service
      SecurityManager.runAs
      1. weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
      1 frame
    6. weblogic.time.common
      ScheduledTrigger.execute
      1. weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
      2. weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
      2 frames
    7. weblogic.kernel
      ExecuteThread.run
      1. weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
      2. weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
      2 frames