GeeCON Prague 2014*
The moose likes BEA/Weblogic and the fly likes JNDI and javax.naming. CommunicationException Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "JNDI and javax.naming. CommunicationException" Watch "JNDI and javax.naming. CommunicationException" New topic
Author

JNDI and javax.naming. CommunicationException

Paul Rhoades
Greenhorn

Joined: Aug 01, 2002
Posts: 20
I get the following exception when trying to connect from a client app to a WebLogic JNDI server. Any pointers would be great...
javax. naming. CommunicationException.
Root exception is java.net. ConnectException: http://x.x.x.x:7001: Destination unreachable; nested exception is: java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'w2w405.corp.lch.com', port: '7001'; No available router to destination
at weblogic.rjvm. RJVMFinder.findOrCreate(RJVMFinder.java:173) at weblogic.rjvm. ServerURL.findOrCreateRJVM(ServerURL.java:262) at weblogic.jndi.
WLInitialContextFactoryDelegate. getInitialContext(WLInitialContextFactoryDelegate. java:323)
Chris Mathews
Ranch Hand

Joined: Jul 18, 2001
Posts: 2712
Your problem is that you are trying to get an JNDI context over HTTP. This is not going to work unless you have HTTP Tunneling enabled. What you probably want is to use either T3(WebLogic's proprietary protocol) or IIOP.
Paul Rhoades
Greenhorn

Joined: Aug 01, 2002
Posts: 20
Sorry, I should have said I've tried both protocols (t3 and http) and get the same problem?
javax.naming.CommunicationException. Root exception is java.net.ConnectException: t3://x.x.x.x:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:173)
Birendar S Waldiya
Greenhorn

Joined: Dec 02, 2003
Posts: 3
I too wa getting same error bi yaa without HttpTunneling enabled weblogic does not support http protocol for look up of context we have to change protocol to t3
Birendar S Waldiya
Greenhorn

Joined: Dec 02, 2003
Posts: 3
But now i am getting
javax.naming.NameNotFoundException: Unable to resolve 'Hello' Resolved:
its not able to resolv the bean name any idea?
prasanna kanth
Greenhorn

Joined: May 14, 2006
Posts: 28
The error comes, only the reason on Administrative Object not created properly, create the proper JNDI name in you server, the same name use it for the look..

With cheers,
PrasannA
 
GeeCON Prague 2014
 
subject: JNDI and javax.naming. CommunicationException