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

Oracle Community | 3004 | 1 decade ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Tunneling result not OK,

    Oracle Community | 1 decade ago | 3004
    java.net.ProtocolException: Tunneling result not OK, result: 'DEAD', id: '15'
  2. 0

    Tunneling result not OK,

    Google Groups | 1 decade ago | Ohto Rainio
    java.net.ProtocolException: Tunneling result not OK, result: 'DEAD', id: '15'
  3. 0

    Tunneling result not OK,

    Google Groups | 1 decade ago | Ohto Rainio
    java.net.ProtocolException: Tunneling result not OK, result: 'DEAD', id: '15'
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Tunneling result not OK,

    Oracle Community | 1 decade ago | 3004
    java.net.ProtocolException: Tunneling result not OK, result: 'DEAD', id: '15'

    Root Cause Analysis

    1. java.net.ProtocolException

      Tunneling result not OK, result: 'DEAD', id: '15'

      at weblogic.rmi.internal.BasicOutboundRequest.sendReceive()
    2. weblogic.rmi.internal
      BasicOutboundRequest.sendReceive
      1. weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
      1 frame
    3. weblogic.rmi.cluster
      EntityRemoteRef.invoke
      1. weblogic.rmi.cluster.EntityRemoteRef.privateInvoke(EntityRemoteRef.java:144)
      2. weblogic.rmi.cluster.EntityRemoteRef.invoke(EntityRemoteRef.java:115)
      2 frames
    4. weblogic.rmi.internal
      ProxyStub.invoke
      1. weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
      1 frame
    5. Unknown
      $Proxy10.calculator
      1. $Proxy10.calculator(Unknown Source)
      1 frame
    6. com.util
      Loader$2.run
      1. com.util.Loader$2.run(Loader.java:811)
      1 frame