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.

Symptom

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.

java.net.ConnectException: t3://myserver:8000: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:49)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:773)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:363)
at weblogic.jndi.Environment.getContext(Environment.java:307)
at weblogic.jndi.Environment.getContext(Environment.java:277)

Cause

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.

Solution

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

References

None


No comments:

Post a Comment