PK67604: PERFORMANCE ISSUE WHEN MAKING JAVA: NAMESPACE INDIRECT JDNI LOOKUPS

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 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.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
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.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: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• A performance issue in WebSphere Application Server v6.0.2 has
  been identified while running a testcase making repetive
  indirect JNDI calls to the java: namespace.  The same testcase
  doing a direct JNDI lookup does not experience the problem.
  
  This testcase ran without problem on multiple WebSphere
  Application Server v5.1.1 cumulative fixpack versions.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere Application Server   *
  *                  V6.0.2 and V6.1 using java: name space      *
  ****************************************************************
  * PROBLEM DESCRIPTION: A performance issue exists for          *
  *                      repetitive java: name space lookups     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In Application Server v6.0.2, the java: name space performance
  enhancement for repetitive lookups does not work if there is a
  direct JNDI lookup prior to the java: name space lookup for
  the same JNDI name.  This only applies to cacheable references
  as the enhancement only improves the lookup performance for
  cacheable references.
  
  In Application Server v6.1, the java: name space performance
  enhancement does not work for both with or without a prior
  direct JNDI lookup.
  

Problem conclusion

• The java: name space enhancement mechanism defect is fixed by
  caching the cacheable reference in JNDI cache for both the
  6.0.2 and 6.1 releases.  An issue in deferring cache creation
  is also fixed in V6.1. Performance improvements are seen in a
  testcase making repetitive indirect lookups for both V6.0.2
  and V6.1 releases.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 6.0.2.31 and 6.1.0.21.  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

  WEBSPH APP SERV

• Fixed component ID

  5724J0800

Applicable component levels

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60P PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R60Z PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP