JNDI lookup fails with two WebSphere Application servers on same machine
 Technote (troubleshooting)
 
Problem(Abstract)
If the user interops two IBM® WebSphere® Application Servers on the same machine, JNDI lookup might fail if the two servers have the name servername, for example, server1.

This also could also happen if the user creates two servers in WebSphere Studio Application Developer as WebSphere Studio Application Developer will automatically assign each server with scope /localhost/server1.
 
Cause
APAR PQ81860 has been opened for this issue, but it will not be in the official fix as it may break WebSphere interOp.
 
Resolving the problem
The user should name servers with different names if both servers are on the same machine.

For WebSphere Studio Application Developer V5.1.2 or later user can use the following workaround:

Once WebSphere Studio Application Developer is open, choose the server perspective, under server configuration click on the port tag. Go to the bottom and it should have ORB bootstrap settings (port and hostname). Make sure the two servers have different ports, name one server localhost and the other with the actual hostname. Then use those for lookup. This will fix the JNDI lookup conflict in the WebSphere Studio Application Developer environment.

 
 
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.2
Software edition:
Reference #: 1196235
IBM Group: Software Group
Modified date: Aug 30, 2007