java.rmi.ConnectException

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 web448

  • via Google Groups by leslie.mampe, 1 year ago
    No available router to destination
  • via Oracle Community by 3004, 1 year ago
    No available router to destination
  • via Oracle Community by 3004, 1 year ago
    No available router to destination
  • Stack trace

    • java.rmi.ConnectException: No available router to destination at weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:1167) at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:378) at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330) at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228) at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188) at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180) at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149) at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:232) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:174) at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:123) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:668) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246) at javax.naming.InitialContext.init(InitialContext.java:222) at javax.naming.InitialContext.<init>(InitialContext.java:178) at vc.test.LoggedUserTestClient2.<init>(LoggedUserTestClient2.java:41) at vc.test.LoggedUserTestClient2.main(LoggedUserTestClient2.java:2259)

    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.