weblogic.rmi.ConnectException: Failed to create socket to: -1766060154911404862S10.36.7.68:[7005,7005,7002,7002,7005,-1] using protocol t3]

Oracle Community | 3004 | 2 decades ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    PeerGoneException  + Undeclared checked exception in 5.1 sp9

    Oracle Community | 2 decades ago | 3004
    weblogic.rmi.ConnectException: Failed to create socket to: -1766060154911404862S10.36.7.68:[7005,7005,7002,7002,7005,-1] using protocol t3]

    Root Cause Analysis

    1. weblogic.rmi.ConnectException

      Failed to create socket to: -1766060154911404862S10.36.7.68:[7005,7005,7002,7002,7005,-1] using protocol t3]

      at weblogic.cluster.replication.ReplicationManager_WLStub.create()
    2. weblogic.cluster.replication
      ReplicationManager.register
      1. weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:108)
      2. weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:436)
      3. weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:617)
      3 frames
    3. weblogic.servlet.internal
      SessionContext.getNewSessionInstance
      1. weblogic.servlet.internal.session.ReplicatedSession.<init>(ReplicatedSession.java:115)
      2. weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:56)
      3. weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(SessionContext.java:352)
      3 frames
    4. Atmosphere weblogic
      ServletRequestImpl.getSession
      1. weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:1341)
      2. weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1233)[att1.html]
      2 frames