java.net.ProtocolException: unrecognized response from proxy: 'HTTP/1.0 403 Tunnel or SSL Forbidden'; No available router to destination]

Oracle Community | 860008 | 4 years ago
  1. 0

    unable to start Admin Server

    Oracle Community | 4 years ago | 860008
    java.net.ProtocolException: unrecognized response from proxy: 'HTTP/1.0 403 Tunnel or SSL Forbidden'; No available router to destination]
  2. 0

    can we please conclude that Weblogic... :: JetBrains Developer Community

    jetbrains.com | 1 year ago
    java.net.ProtocolException: unrecognized response from proxy: 'HTTP/1.0 403 Forbidden'; No available router to destination]
  3. 0

    JMS C API and HTTP JMS URI Error: "Could not create a context"

    Google Groups | 1 decade ago | Tarang Patel
    java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'myhost.mydomain' and port: '1180' a WebLogic Server?; No available router to destination]
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    WebLogic Scripting « WebLogic

    middlewaremagic.com | 1 year ago
    java.net.ProtocolException: Tunneling result unspecified – is the HTTP s erver at host: ‘WLSHostName’ and port: ‘7001’ a WebLogic Server?; No available router to destination]
  6. 0

    JMS C API and HTTP  JMS URI Error: "Could not create a context"

    Oracle Community | 1 decade ago | 666705
    java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'myhost.mydomain' and port: '1180' a WebLogic Server?; No available router to destination]

    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

      unrecognized response from proxy: 'HTTP/1.0 403 Tunnel or SSL Forbidden'; No available router to destination]

      at weblogic.jndi.internal.ExceptionTranslator.toNamingException()
    2. weblogic.jndi.internal
      ExceptionTranslator.toNamingException
      1. weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
      1 frame
    3. weblogic.jndi
      WLInitialContextFactory.getInitialContext
      1. weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
      2. weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
      3. weblogic.jndi.Environment.getContext(Environment.java:315)
      4. weblogic.jndi.Environment.getContext(Environment.java:285)
      5. weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
      5 frames
    4. Java RT
      InitialContext.<init>
      1. javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      2. javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
      3. javax.naming.InitialContext.init(InitialContext.java:223)
      4. javax.naming.InitialContext.<init>(InitialContext.java:197)
      4 frames
    5. weblogic.management.remote
      ClientProviderBase.makeConnection
      1. weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:177)
      1 frame