Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 3004, 1 year ago
Failed to create socket to: -1766060154911404862S10.36.7.68:[7005,7005,7002,7002,7005,-1] using protocol t3
via Google Groups by Timo Hoepfner, 2 years ago
Failed to create socket to: - 3054947444858285486C172.31.2.139 using protocol t3
via Oracle Community by 3004, 2 years ago
Failed to create socket to: -6284328634002331038S192.168.128.80:[7001,7001,7002,7002,7001,-1] using protocol t3
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.(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)