This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes BEA/Weblogic and the fly likes javax.naming.CommunicationException: Destination unreachable Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "javax.naming.CommunicationException: Destination unreachable" Watch "javax.naming.CommunicationException: Destination unreachable" New topic
Author

javax.naming.CommunicationException: Destination unreachable

Toyan Harvey
Greenhorn

Joined: Feb 15, 2010
Posts: 4
Hey guys, I've seen posts about this error but it appears I'm doing everything correct. The url i'm sending to get the context of the server is "t3://xxx.xxxx.xxxx.xxxx:7001".

I may be confused on what I'm doing. I have 2 weblogic servers (2 different machines). A web app on one and a MDB on the other. In the webapp I want to send a message to one of the mdb server jms queues. When I send the url to my get context method I get the following exception

javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://172.16.85.37:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection timed out: connect; No available router to destination]

Anyone have any ideas on what I should check out to debug this problem.

Thanks
Deepak Bala
Bartender

Joined: Feb 24, 2006
Posts: 6661
    
    5

It means the network connection to the desired location is unreachable. Wrong IP address / port ?


SCJP 6 articles - SCJP 5/6 mock exams - More SCJP Mocks
 
wood burning stoves
 
subject: javax.naming.CommunicationException: Destination unreachable
 
Similar Threads
JNDI and javax.naming. CommunicationException
java.net.ConnectException
EJB 3.0 - NoInitialContextException
javax. naming. CommunicationException
Problem in starting Managed weblogic server