Monday, January 10, 2011

Connection refused: No available router to destination

This is a simple symptom-cause-solution blog entry only. I hope these blogs will help fellow administrators.


The following exception occurs in WebLogic server logs. Most likely to occur during WebLogic server start-up, but similar exceptions may occur at other times. t3://myserver:8000: Destination unreachable; nested exception is: Connection refused: connect; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(
at weblogic.jndi.Environment.getContext(
at weblogic.jndi.Environment.getContext(


This message (Connection refused: connect; No available router to destination) is a kind of "catch-all" exception message. There may be a number of causes, but essentially the application or server is attempting to establish a connection, but is unable to.


Check the following:
  • The destination name resolves to an IP address
  • The destination is "pingable"
  • The destination port is open (use telnet, for example)