PQ51608: JNDI CACHE WITH INITIAL CONTEXT INFO IS NOT BEING CLEARED AS SPECIFIED AND SUBSEQUENT CLIENT ACCESS SAME SERVER


APAR

APAR status
Closed as program error.

Error description
Clients continue to tie themselves to shutdown appservers even
when trying to get new initial contexts (caching set to cleared)
It appears that WAS client IIOP code is caching some, but not
all, info about initial context request for the life of the JVM,
such as any subsequent initial context requests specifying the
same IIOP address will always be directed to the same appserver.
Local fix
Problem summary
Clients continue to tie themselves to shutdown appservers even
when trying to get new initial contexts (caching set to cleared)
It appears that WAS client IIOP code is caching some, but not
all, info about initial context request for the life of the JVM,
such as any subsequent initial context requests specifying the
same IIOP address will always be directed to the same appserver.
Problem conclusion
Temporary fix
Comments
APAR information
APAR numberPQ51608
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2001-08-17
Closed date2001-08-22
Last modified date2001-08-22

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:of the following:


Modules/Macros
ORB
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED AI
Fixed component ID5648C8400

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ51608
IBM Group: Software Group
Modified date: 2001-08-22