WLEJBInitialContext().lookup() returns CommunicationException and UnknownHostException: null (Doc ID 2461016.1)

Last updated on OCTOBER 27, 2022

Applies to:

Symptoms

WLEJBInitialContext().lookup() returns CommunicationException:

javax.naming.CommunicationException: Could not establish a connectionManager with -186494016306088063S:127.0.0.1:[7001,-1,-1,-1,-1,-1,-1]:WHATEVER-ADF:AdminServer, t3://127.0.0.1:7001 java.rmi.ConnectException:
Destination not reachable using: 'Default[t3]:t3(t3):null:-1:127.0.0.1:-1'; [RJVM:000576]No available router to destination.; nested exception is: 
 java.rmi.ConnectException: [RJVM:000576]No available router to destination.; nested exception is: 
 java.rmi.ConnectException: Destination not reachable using: 'Default[t3]:t3(t3):null:-1:127.0.0.1:-1'; [RJVM:000576]No available router to destination.; nested exception is: 

Error log shows:

Exception in thread "main" javax.naming.ServiceUnavailableException: null [Root exception is java.net.UnknownHostException: null]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:38)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:889)
...
at oracle.jbo.client.remote.ejb.wl.WLEJBInitialContext.createJboHome(WLEJBInitialContext.java:44)
...
Caused by: java.net.UnknownHostException: null
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)

EJB client code:

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.