3549753 - javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target; No available router to

After Performing SP Level update, JMS receiver channel is failing with the following error:

[EXCEPTION]
javax.naming.CommunicationException: Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms. 

XXXXXXXXXXXXXXXXXXXXXX: Destination XXX unreachable.; nested exception is: 
javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate); No available router to destination.; nested exception is: 
java.rmi.ConnectException: No available router to destination. [Root exception is java.net.ConnectException: XXXXXXXXXXXXXXXXXXXX: Destination XXX unreachable.; nested exception is: 
javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate); No available router to destination.; nested exception is: 
java.rmi.ConnectException: No available router to destination.]
at weblogic.jndi.WLInitialContextFactoryDelegate.throwRetryException(WLInitialContextFactoryDelegate.java:467)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:403)
at weblogic.jndi.Environment.getContext(Environment.java:353)
at weblogic.jndi.Environment.getContext(Environment.java:322)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:131)
at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:64)
at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:45)
at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:694)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
at javax.naming.InitialContext.init(InitialContext.java:244)
at javax.naming.InitialContext.<init>(InitialContext.java:216)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:76)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doBeforeConnect(JndiConnectorImpl.java:49)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:225)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:209)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:442)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:183)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:995)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: java.net.ConnectException: XXXXXXXXXXXXXXXX: Destination XXX unreachable.; nested exception is: 
javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate); No available router to destination.; nested exception is: 
java.rmi.ConnectException: No available router to destination.
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:258)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:174)
at weblogic.rjvm.ClientServerURL.findOrCreateRJVM(ClientServerURL.java:179)
at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:354)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:365)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:143)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:350)
... 21 more
Caused by: java.rmi.ConnectException: Destination XXX unreachable.; nested exception is: 
javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate); No available router to destination.; nested exception is: 
java.rmi.ConnectException: No available router to destination.
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:566)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:369)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:358)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:179)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:281)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteCluster(RJVMFinder.java:353)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:248)
... 27 more
Caused by: java.rmi.ConnectException: No available router to destination.
at weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:1888)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:547)
... 33 more

SAP NetWeaver All versions

 certificates,, jre/lib/security/cacerts, restart, SP Level update,JMS, JMS receiver channel, connection exception, target URL, javax.naming.CommunicationException, JNDI context, SSLHandshakeException, protocol disabled, cipher suites inappropriate, router unavailable, java.rmi.ConnectException, weblogic.jndi, JNDI initialization, sapjvm , KBA , BC-XI-CON-JMS , JMS Adapter , Problem