weblogic.rmi.ConnectException

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

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 web9

  • Failed to create socket to: -1766060154911404862S10.36.7.68:[7005,7005,7002,7002,7005,-1] using protocol t3
  • via Google Groups by Timo Hoepfner, 1 year ago
    Failed to create socket to: - 3054947444858285486C172.31.2.139 using protocol t3
  • via Oracle Community by 3004, 1 year ago
    Failed to create socket to: -6284328634002331038S192.168.128.80:[7001,7001,7002,7002,7001,-1] using protocol t3
  • Stack trace

    • weblogic.rmi.ConnectException: Failed to create socket to: -1766060154911404862S10.36.7.68:[7005,7005,7002,7002,7005,-1] using protocol t3 at weblogic.rjvm.ConnectionManager.getOutputStream(ConnectionManager.java:1056) at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:447) at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:397) at weblogic.rmi.extensions.AbstractRemoteObjectReference.getRequest(AbstractRemoteObjectReference.java:71) at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:82) at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:436) at weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:617) at weblogic.servlet.internal.session.ReplicatedSession.<init>(ReplicatedSession.java:115) at weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:56) at weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(SessionContext.java:352) at weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:1341) at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1233)

    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.