PQ86458: WebSphere WLM object reference cache invalid

APAR status
Closed as program error.

Error description
Problem Description:
Chain of events
1)Websphere 4 advanced edition EJB client is connected to a
WebSphere 5 network deployment cell.

2)Websphere 5 cell is stopped and restarted during normal 4hr
mainentance window.  WebSphere 4 client has little or no
traffice during maintenance window but is left running.

3)Websphere 5 server during restart are at same IP address but
different port numbers due to app server start sequencing.

4)Websphere 4 client still has old WLM information prior to the
restart and tries to connect to EJB app server with old object
reference information.  WebSphere 5 server that recieves
connection is not the

serving application server and throws:
java.rmi.NoSuchObjectException: CORBA OBJECT_NOT_EXIST
1229126659 No;
nested exception is:   org.omg.CORBA.OBJECT_NOT_EXIST:   minor
code:
1229126659  completed: No; with message:CORBA OBJECT_NOT_EXIST
1229126659 No; nested exception is:
org.omg.CORBA.OBJECT_NOT_EXIST:
minor code: 1229126659  completed: No
The VMCID is 0x4942fc03.  Object key does not exist.
This is similar to a WebSphere 5.x client efix for with the same
symptoms.  Please see 
PQ78295 and PMR 36213,500.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of WLM    *
*                 or Workload Managment.                       *
****************************************************************
* PROBLEM DESCRIPTION: A org.omg.CORBA.OBJECT_NOT_EXIST:       *
*                      BAD_SERVER_ID exception is thrown back  *
*                      to a client when the clustermembers     *
*                      are recycled.                           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a client application holds onto a WLMable reference
(a home object or a remote reference) and all of the
clustermembers are recycled, a
org.omg.CORBA.OBJECT_NOT_EXIST: BAD_SERVER_ID
exception is thrown when the client attempts to use
one of the held references after the clustermembers
are available for service again.
Problem conclusion
The check for a specific exception was not checked and as a
result caused a problem in a very specific environment.
Temporary fix
Recycle the client side application.
Comments
APAR information
APAR number PQ86458
Reported component name WEBSPHERE AES S
Reported component ID 5630A2302
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2004-03-22
Closed date 2004-06-10
Last modified date 2004-06-10

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
wlm          

Fix information

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ86458
IBM Group: Software Group
Modified date: Jun 10, 2004