Non-java client receives BAD_SERVER_ID(2) and/or OBJECT_NOT_EXIST errors while accessing an EJB
 Technote (troubleshooting)
 
Problem(Abstract)
When fixed ORB ports are used, the IOR returned to the client, when seeking access to an EJB, contain all the hosts and ports for all the EJB's in the cell and node agents, rather than just the host and port of the EJB.

This can give rise to problems with non-java™ clients, but these extra entries in the LSD list can also cause WLM to route requests to non-LSDs (like application servers) which can, in turn, lead to CORBA errors such as BAD_SERVER_ID(2) and/or OBJECT_NOT_EXIST.
 
Cause
The WLM code creates spurious entries in the LSDAddress lists which end up
on the AlternateIIOPAddress.

The basic problem is that when fixed ports are used, servers then have an ORB_LISTENER_ADDRESS entry in the serverindex.xml, and our code that made the LSDAddress list, did not check to see if the server was a nodeagent, or not, because (typically) other servers do not have ORB_LISTENER_ADDRESS entries, just the Node Agents. This has been busted for some time.
 
Resolving the problem
APAR PK02330 was created to resolve this problem.
The fix for this APAR is currently targeted for inclusion in fixpack 5.0.2.11 and 5.1.1.4.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
Historical Number
70217
082
000
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Workload Management (WLM)
Operating system(s): AIX
Software version: 5.1.1
Software edition:
Reference #: 1207465
IBM Group: Software Group
Modified date: Sep 3, 2007