JNDI lookups fail after node agent is restarted
 Technote (troubleshooting)
 
Problem(Abstract)
In a WebSphere® Application Server V5 Network Deployment (ND) environment, JNDI lookups of resources may fail after the node agent is restarted. The same JNDI lookups would succeed before the node agent was restarted, and would also succeed after the application servers are restarted.

The problem would only occur between the time that the node agent is restarted and the application servers are restarted. The following error would occur:

javax.naming.NamingException: Error during resolve. Root exception is org.omg.CORBA.OBJECT_NOT_EXIST: vmcid: IBM minor code: C02 completed: No

This is a known problem on all levels of WebSphere Application Server V5 up to and including V5.0.2.10 and V5.1.1.4. However it only occurs if a static value is used for the ORB_LISTENER_ADDRESS of the application server.
 
Cause
The problem is caused by two WebSphere Application Server defects that are addressed by APARs PK02330 and PK03189.
 
Resolving the problem
To resolve the problem, install Cumulative Fix 11 (V5.0.2.11) or higher for WebSphere Application Server V5.0.2, or install Cumulative Fix 5 (V5.1.1.5) or higher for WebSphere Application Server V5.1.1.

A work-around to the problem is to specify a dynamic ORB_LISTENER_ADDRESS for the application server. However, this will cause problems for you if there is a firewall between the JNDI client and the server. If there is no firewall, you can specify a dynamic ORB_LISTENER_ADDRESS in the Administrative Console:

  1. Expand Servers
  2. Select application servers
  3. Select an application server (you will need to make this change for every application server in your environment)
  4. Under Additional Properties, select End Points
  5. Select ORB_LISTENER_ADDRESS
  6. Change the value of the Port to 0
  7. Click OK and save your changes
  8. Restart the application server

You can also change the ORB_LISTENER_ADDRESS by editing your serverindex.xml file. The serverindex.xml can be found in the <WebSphere Application Server install_root>/config/cells/<cell name>/nodes/<node name> directory. There will be one for each node. When you open the file in a text editor, look for:

<specialEndpoints xmi:id="NamedEndPoint_1128620739879" endPointName="ORB_LISTENER_ADDRESS">
<endPoint xmi:id="EndPoint_1128620739879" host="localhost" port="0"/>
(note that the numbers after "NamedEndPoint" will be different on your system)

Change the port from its current value to 0. Then save the file and restart your WebSphere Application Server processes (application server, node agent, deployment manager).
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > JNDI/Naming
Operating system(s): Windows
Software version: 5.1.1
Software edition:
Reference #: 1223179
IBM Group: Software Group
Modified date: Nov 18, 2005