APAR status
Closed as program error.
Error description
WebSphere version 5.0.2.4 AIX
The problem occurs when a lookup is needed to be performed on
both local and remote servers. For example, if the lookup from
the nodeAgent server root on a lookup name
"cell/clusters/anyCluster/ejb/myEJB".
"cell/clusters" are local contexts, but "anyCluster" is a remote
context so does "anyCluster/ejb". In that case, Naming server
only passed back the remote context IDs, but not all context
IDs, to Naming client. That resulted in the lookup result not
being cached in the JNDI cache.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server V5 users using *
* the JNDI Cache of Naming. *
****************************************************************
* PROBLEM DESCRIPTION: The problem occurs when a lookup *
* involves both local and remote *
* context/objects. For example, if the *
* lookup with a lookup name *
* "cell/clusters/anyCluster/ejb/myEJB" *
* performed under the nodeAgent server *
* root, "cell/clusters" are local *
* contexts, but "anyCluster" is a remote *
* context so does "anyCluster/ejb". In *
* that case, Naming server only passed *
* back the remote context IDs, but not *
* all context IDs, to Naming client. *
* That results in the lookup result not *
* being cached in the JNDI cache. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The problem occurs when a lookup involves both local and remote
context/objects. For example, if the lookup with a lookup name
"cell/clusters/anyCluster/ejb/myEJB" performed under the
nodeAgent server root, "cell/clusters" are local contexts, but
"anyCluster" is a remote context so does "anyCluster/ejb". In
that case, Naming server only passed back the remote context
IDs, but not all context IDs, to Naming client. That results
in the lookup result not being cached in the JNDI cache.
Problem conclusion
The fix is to have a new method added in the Naming server
code to concatenate both local and remote context IDs. Then
the Naming server passes all context IDs back to the Naming
client to make the lookup result be cached correctly.
Temporary fix Comments
APAR information |
APAR number |
PQ92347 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-08-03 |
Closed date |
2004-08-23 |
Last modified date |
2004-08-23 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|