javax.net.ssl.SSLHandshakeException

[Security:090497]HANDSHAKE_FAILURE alert received from 10.51.0.3 - 10.51.0.3. Check both sides of the SSL configuration for mismatches in supported ciphers, supported protocol versions, trusted CAs, and hostname verification settings.; No available router to destination

Solutions on the web3313

  • via Oracle Community by 3004, 11 months ago
    [Security:090497]HANDSHAKE_FAILURE alert received from 10.51.0.3 - 10.51.0.3. Check both sides of the SSL configuration for mismatches in supported ciphers, supported protocol versions, trusted CAs, and hostname verification settings.; No available router to destination
  • via hivmr.com by Unknown author, 1 year ago
    [Security:090497]HANDSHAKE_FAILURE alert received from 10.51.0.3 - 10.51.0.3. Check both sides of the SSL configuration for mismatches in supported ciphers, supported protocol versions, trusted CAs, and hostname verification settings.; No available router to destination
  • via Oracle Community by user10939158, 1 year ago
    [Security:090497]HANDSHAKE_FAILURE alert received from admin_server - nn.nn.nn.nn. Check both sides of the SSL configuration for mismatches in supported ciphers, supported protocol versions, trusted CAs, and hostname verification settings.; No available router to destination]
  • Stack trace

    • javax.net.ssl.SSLHandshakeException: [Security:090497]HANDSHAKE_FAILURE alert received from 10.51.0.3 - 10.51.0.3. Check both sides of the SSL configuration for mismatches in supported ciphers, supported protocol versions, trusted CAs, and hostname verification settings.; No available router to destination at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199) at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239) at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243) at javax.naming.InitialContext.init(InitialContext.java:219) at javax.naming.InitialContext.<init>(InitialContext.java:195) at ros.services.jms.RISJMSConnection.<init>(RISJMSConnection.java:42) at ros.services.jms.JMSFactory.getRISJMSMessage(JMSFactory.java:70) at ros.services.jms.TestJMS.connect(TestJMS.java:15) at ros.utils.LogStartup.startup(LogStartup.java:98) at ros.utils.LogStartup.main(LogStartup.java:119) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at weblogic.j2ee.AppLifecycleListenerInternal.invokeMain(AppLifecycleListenerInternal.java:61) at weblogic.j2ee.AppLifecycleListenerInternal.preStart(AppLifecycleListenerInternal.java:34) at weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:50) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(J2EEApplicationContainer.java:4721) at weblogic.j2ee.J2EEApplicationContainer.notify(J2EEApplicationContainer.java:4683)

    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 are the first who have seen this exception. Write a tip to help other users and build your expert profile.