EJB3: JNDI connection problem managed server

Question

Hi all,
In a JUnit test, I tried to look up a Session EJB from a remote managed server:
Hashtable<String, String> props = new Hashtable<String, String>();
props.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
props.put(javax.naming.Context.PROVIDER_URL, "t3://server1.ux.yucom.es:1751");
props.put(javax.naming.Context.SECURITY_PRINCIPAL, "userName");
props.put(javax.naming.Context.SECURITY_CREDENTIALS, "pwd");
props.put(weblogic.jndi.WLContext.ALLOW_EXTERNAL_APP_LOOKUP, "true");
InitialContext context = new InitialContext(props);
Command command = (Command) context.lookup(jndiName);
But the code already fails while instantiating the InitialContext, because of a connection problem:
Caused by: java.net.ConnectException: t3://server1.ux.yucom.es:1751: Destination unreachable; nested exception is:
     java.net.ConnectException: Connection timed out: connect; No available router to destination
     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:203)
     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:352)
     ... 34 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
     java.net.ConnectException: Connection timed out: connect; No available router to destination
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:251)
     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:225)
     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:188)
     ... 36 more
I'm able to connect to the the Admin server... In this case I receive a javax.naming.NameNotFoundException, obviously, since the remote EJB is only targetted on the managed server and not on the admin.
This is confirmed by following little test on the command line:
java -cp %WL_HOME%\server\lib\weblogic.jar weblogic.Admin -url t3://server1.ux.yucom.es:1700 -username <user> -password <pwd> PING
=> OK, packets received
java -cp %WL_HOME%\server\lib\weblogic.jar weblogic.Admin -url t3://server1.ux.yucom.es:1751 -username <user> -password <pwd> PING
=> Failure:
Failed to connect to server1.ux.yucom.es:1751: Destination unreachable; nested exception is:
java.net.ConnectException: Connection timed out: connect; No available router to destination
Does anyone has an idea why the connection to the managed server fails??
Is it a configuration problem in WebLogic?
Thx a lot!
Wim.

Answer 1

Hi,
Are you able to Remotely Access any Simple Web Application deployed on "server1.ux.yucom.es:1751".
Example: http://server1.ux.yucom.es:1751/TestApp/index.jsp
If NOT: Means Some where there is a problem with the Port...Just for testing Try Changin Manged Server port to Default HTTP Port (80).
If Yes: Then there are chances that Your Box is not allowing any t3-Protocol Traffic on 1751 Port. Just for Testing Enable HTTP Tunneling on this Server from Admin Console
AdminConsole --> Home-->Summary Of Servers --->ManagedServer1 ---> Protocol (Tab) ---> HTTP (SubTab) --->Enable Tunneling (Check This Check Box)    Save the changes.
And then After restarting your Server ... Try to ping your Server using:
java -cp %WL_HOME%\server\lib\weblogic.jar weblogic.Admin -url http://server1.ux.yucom.es:1751 -username <user> -password <pwd> PING
In the Above command Use HTTP protocol instead of T3. If Now u are able to Ping the Server means Your Port 1751 was not allowing any other Protocol except HTTP.
Thanks
Jay SenSharma
http://middlewaremagic.com/weblogic  (Middleware magic Is Here)