java.net.ProtocolException: Tunneling result not OK, result: 'DEAD', id: '15'

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 Google Groups by Ohto Rainio, 1 year ago
Tunneling result not OK, result: 'DEAD', id: '15'
via Google Groups by Ohto Rainio, 2 years ago
Tunneling result not OK, result: 'DEAD', id: '15'
via Oracle Community by 3004, 1 year ago
Tunneling result not OK, result: 'DEAD', id: '15'
via Oracle Community by 3004, 1 year ago
Tunneling result not OK, result: 'DEAD', id: '15'
via Google Groups by Michael Gogins, 2 years ago
Tunneling result not OK, result: 'DEAD', id: '39'
java.net.ProtocolException: Tunneling result not OK, result: 'DEAD', id: '15'
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
at weblogic.rmi.cluster.EntityRemoteRef.privateInvoke(EntityRemoteRef.java:144)
at weblogic.rmi.cluster.EntityRemoteRef.invoke(EntityRemoteRef.java:115)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at undefined.$Proxy10.calculator(Unknown Source)
at com.util.Loader$2.run(Loader.java:811)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.