PK87446: NAMENOTFOUNDEXCEPTION FOR RESOURCE ON A SINGLE SERVER IN A CLUSTER

6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• A lookup for a resource defined on a single member of a cluster
  gets a NameNotFoundException on 6.1.0.21. The same configuration
  works on previous versions.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V6.1                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:  The node root naming context is WLM    *
  *                       enabled                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a new naming context is created, the ServantManager of
  the parent context was used to register the new context
  instead of the ServantManager of the new context. The new
  context's and the parent's ServantManager are not necessarily
  the same. For example, the parent context could be WLM enabled
  but the new child context is not.
  

Problem conclusion

• Used the new context's ServantManager to registerContext
  instead of using the parent's ServantManager.
  .
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.29. Please refer to the Recommended Updates page
  for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

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

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP

• R61P PSY

     UP