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

Oracle Community | 3004 | 1 decade ago
  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,

    Oracle Community | 1 decade ago | 3004
    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,

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

    JMS tunneling over HTTP

    Google Groups | 1 decade ago | Michael Gogins
    java.net.ProtocolException: Tunneling result not OK, result: 'DEAD', id: '39'

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.net.ProtocolException

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

      at weblogic.rmi.internal.ProxyStub.invoke()
    2. weblogic.rmi.internal
      ProxyStub.invoke
      1. weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
      1 frame
    3. Unknown
      $Proxy10.calculator
      1. $Proxy10.calculator(Unknown Source)
      1 frame
    4. com.util
      Loader$2.run
      1. com.util.Loader$2.run(Loader.java:811)
      1 frame