java.net.ProtocolException

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

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web205

  • via Oracle Community by 860008, 1 year ago
    unrecognized response from proxy: 'HTTP/1.0 403 Tunnel or SSL Forbidden'; No available router to destination
  • unrecognized response from proxy: 'HTTP/1.0 403 Tunnel or SSL Forbidden'; No available router to destination
  • unrecognized response from proxy: 'HTTP/1.0 403 Forbidden'; No available router to destination]
  • Stack trace

    • java.net.ProtocolException: unrecognized response from proxy: 'HTTP/1.0 403 Tunnel or SSL Forbidden'; No available router to destination at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464) at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315) at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254) at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197) at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238) at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200) at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170) at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153) at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340) at weblogic.jndi.Environment.getContext(Environment.java:315) at weblogic.jndi.Environment.getContext(Environment.java:285) at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.<init>(InitialContext.java:198) at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:177) at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:83) at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247) at oracle.eclipse.tools.weblogic.server.internal.WlsJMXHelper.createConnector(WlsJMXHelper.java:269) at oracle.eclipse.tools.weblogic.server.internal.WlsJMXHelper.connectToJMX(WlsJMXHelper.java:76) at oracle.eclipse.tools.weblogic.server.internal.WlsJMXHelper.getDomainAttribute(WlsJMXHelper.java:139) at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.validateRemote(WlsJ2EEDeploymentHelper.java:1688) at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.validateRemote(WeblogicServerBehaviour.java:2648)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.