javax.net.ssl.SSLException

Received fatal alert: certificate_unknown; 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 web761

  • via Oracle Community by Ramesh2011, 11 months ago
    Received fatal alert: certificate_unknown; No available router to destination
  • Received fatal alert: unexpected_message; No available router to destination
  • via blogspot.com by Unknown author, 11 months ago
    Received fatal alert: unexpected_message; No available router to destination
  • Stack trace

    • javax.net.ssl.SSLException: Received fatal alert: certificate_unknown; No available router to destination at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470) at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321) 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.getInitialContext(WLInitialContextFactoryDelegate.java:353) at weblogic.jndi.Environment.getContext(Environment.java:315) at weblogic.jndi.Environment.getContext(Environment.java:285) at weblogic.jndi.Environment.createInitialContext(Environment.java:208) at weblogic.jndi.Environment.getInitialContext(Environment.java:192) at weblogic.jndi.Environment.getInitialContext(Environment.java:170) at com.bea.alsb.platform.weblogic.topology.WlsRemoteServerImpl.getInitialContext(WlsRemoteServerImpl.java:239) at com.bea.alsb.platform.weblogic.topology.WlsRemoteServerImpl.lookupJNDI(WlsRemoteServerImpl.java:76) at com.bea.wli.monitoring.statistics.ALSBStatisticsManager.getRemoteAggregator(ALSBStatisticsManager.java:291) at com.bea.wli.monitoring.statistics.ALSBStatisticsManager.access$000(ALSBStatisticsManager.java:38) at com.bea.wli.monitoring.statistics.ALSBStatisticsManager$RemoteAggregatorProxy.send(ALSBStatisticsManager.java:55) at com.bea.wli.monitoring.statistics.collection.Collector.sendRawSnaphotToAggregator(Collector.java:284) at com.bea.wli.monitoring.statistics.collection.Collector.doCheckpoint(Collector.java:245) at com.bea.wli.monitoring.statistics.collection.Collector$CheckpointThread.doWork(Collector.java:69) at com.bea.wli.monitoring.utils.Schedulable.timerExpired(Schedulable.java:68) at com.bea.wli.timer.ClusterTimerImpl$InternalTimerListener.timerExpired(ClusterTimerImpl.java:255) at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)

    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

    Unknown user
    Once, 11 months ago
    Unknown user
    Once, 1 year ago