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.

  • JMS 6.1 vs 7.0 interoperability
    via by gusano,
  • JMS / WL 5.1 app using Topic on WL 7.0 Cluster
    via by scott lauder,
  • jms / wl 5.1 app and topic on wl 70
    via by slauder,
  • jms / wl 5.1 app and topic on wl 7.0
    via by slauder,
  • weblogicÔõÑùÅäÖÃpoolºÍjndi ??
    via by Unknown author,
    • Connection timed out: connect; No available router to destination [java] at weblogic.rjvm.RJVMFinder.findOrCreate([java] at weblogic.rjvm.ServerURL.findOrCreateRJVM([java] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext([java] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext([java] at weblogic.jndi.WLInitialContextFactory.getInitialContext([java] at javax.naming.spi.NamingManager.getInitialContext([java] at javax.naming.InitialContext.getDefaultInitCtx([java] at javax.naming.InitialContext.init([java] at javax.naming.InitialContext.<init>([java] at com.zilliant.zpm.utils.context.RemoteWLContextFactory.getInitialContext([java] at com.zilliant.zpm.customers.FuManChu.client.ZPMAirAdapter.loadPricerHome(

    Users with the same issue

    Unknown visitor
    Unknown visitor1 times, last one,