java.net.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.

  • WLS sthutdown issue.mmm
    via by 824160,
  • SAF Agent throws ConnectException
    via by 722029,
    • java.net.ConnectException: Connection refused; No available router to destination] at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40) at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:792) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366) at weblogic.jndi.Environment.getContext(Environment.java:315) at weblogic.jndi.Environment.getContext(Environment.java:285) at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.<init>(InitialContext.java:197) at weblogic.jndi.internal.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:70) at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96) at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377) at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856) at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209) at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254) at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412) at javax.naming.InitialContext.lookup(InitialContext.java:392) at oracle.bpel.services.workflow.runtimeconfig.client.RuntimeConfigServiceRemoteClient.getTaskDisplayInfo(RuntimeConfigServiceRemoteClient.java:693)
    No Bugmate found.