PK88110: INVOKING GETCLIENTCOMMANDMGR FROM AN APPLICATION ON A BASE SERVER RESULTS IN AN OUTOFMEMORY ERROR

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

• If an application on a base server invokes getClientCommandMgr
  and passes in an admin client to that same base server JVM, an
  incorrect command manager will be returned.  If the
  application code uses that command manager to invoke
  createCommand, the server can get stuck in an infinite
  connector call loop, and crash with Out-of-Memory errors.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V6.1                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: If an application invokes               *
  *                      getClientCommandMgr followed by         *
  *                      createCommand on a base server, Out     *
  *                      of Memory Errors could appear.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If an application on a base application server needs to invoke
  WebSphere Administrative commands that affect that particular
  base server, it needs to call getCommandMgr to get to
  appropriate command manager.
  
  However, such an application also has the ability to invoke
  getClientCommandMgr and pass in an adminclient to that same
  base server.  If this returned command manager is used to make
  a createCommand invocation, the call never returns.  The
  server gets stuck in an infinite connector loop, and can
  potentially crash with Out of memory errors.
  
  Using getClientCommandMgr in such a situation is incorrect
  usage, and customers are advised to change their code to use
  getCommandMgr instead.
  

Problem conclusion

• This APAR detects incorrect usage of getClientCommandMgr and
  throws an Exception.  This allows for a more graceful failure
  of the getCommandMgr call from the application code as opposed
  to an infinite loop and Out of Memory errors.
  
  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

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP