java.rmi.ConnectException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Trouble with clustering
    via by 3004,
  • Managed server discovery problem
    via by 3004,
  • weblogicÔõÑùÅäÖÃpoolºÍjndi ??
    via by Unknown author,
    • 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:235) at weblogic.jndi.Environment.getContext(Environment.java:135) at weblogic.jndi.Environment.getInitialContext(Environment.java:118) at weblogic.rmi.cluster.BasicReplicaHandler.refreshReplicaList(BasicReplicaHandler.java:394) at weblogic.rmi.cluster.BasicReplicaHandler.failOver(BasicReplicaHandler.java:155)
    No Bugmate found.