Troubleshooting
Problem
A WebSphere Application client is unable to connect to a WebSphere Application Server when trying to do a JNDI lookup of an EJB. The root exception is java.net.UnknownHostException.
Symptom
Trace from the Application Server:
1292951558 at host myHost.company.com >> org.omg.CORBA.COMM_FAILURE: vmcid: 0x49421000 minor code: 40 completed: No
at com.ibm.ws.runtime.workloadcontroller.OrbWorkloadRegulator.getException
(OrbWorkloadRegulator.java:814)
at com.ibm.ws.runtime.workloadcontroller.OrbWorkloadRegulator.handleRequest
ForQuiesceRequestedMode(OrbWorkloadRegulator.java:464)
at com.ibm.ws.runtime.workloadcontroller.OrbWorkloadRegulator.handleRequest
(OrbWorkloadRegulator.java:348)
at com.ibm.ws.runtime.workloadcontroller.
OrbWorkloadRequestInterceptor.receive_request
(OrbWorkloadRequestInterceptor.java:44)
at com.ibm.rmi.pi.InterceptorManager.iterateReceiveRequest
(InterceptorManager.java:748)
In an ORB trace
orbtrc.txt:
13:59:07.063 com.ibm.ws.orbimpl.transport.WSTCPTransportConnection createSocket:635 P=545782:O=0:CT ORBRas[default] createSocket
(String host, int port, InetAddress localInetAddress) is not implemented by this transport. Ignoring the value localInetAddress=localhost/127.0.0.1
13:59:09.327 com.ibm.ws.orbimpl.transport.WSTCPTransportConnection connect:467 P=545782:O=0:CT ORBRas[default] java.net.UnknownHostException: myHost
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:176)
at java.net.Socket.connect(Socket.java:459)
at java.net.Socket.connect(Socket.java:409)
at java.net.Socket.<init>(Socket.java:315)
Cause
In the WebSphere Application Server configuration, the serverindex.xml and plugin-cfg.xml had the shortname (myHost) of the server defined for the host rather than the fully qualified hostname (myhost.domainname.com).
Resolving The Problem
Make sure that machine where the client is running from can resolve the shortname of the server machine WebSphere is running on, for instance, updating the machines "hosts" file.
Or
Manually modify the servers serverindex.xml and plugin-cfg.xml files to contain the fully qualified hostname. This name must still be resolvable from the client server.
Historical Number
90274;500;000
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21198886