PK76863: XLXP PARSER CAUSES MEMORY LEAK WITH LARGE REQUESTS

PK76863; 6.1.0.21: XLXP parser causes memory leak with large requests
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

• New XLXP parser causes a memory leak.
  
  When running internal tests with a request containing
  whitespace, a memory leak might be seen, and eventually can
  hit an OutOfMemoryError.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server users who      *
  *                  have installed a V6.1 Feature Pack          *
  ****************************************************************
  * PROBLEM DESCRIPTION: The SAX parser may leave the            *
  *                      underlying InputStream open,            *
  *                      resulting in an OutOfMemoryError error  *
  ****************************************************************
  * RECOMMENDATION:  Install a fixpack that contains this APAR.  *
  ****************************************************************
  If a SOAP or XML message containing whitespace is passed to the
  SAX parser, and a subtree containing whitespace is skipped,
  the underlying InputStream may be left open, eventually
  resulting in an OutOfMemoryError.
  

Problem conclusion

• The XLXP code was updated to remove the Out of memory condition.
  
  Note that this problem does not occur unless one of the
  feature packs for WebSphere Application Server version 6.1 has
  been installed, such as the Feature Pack for Web Services or
  the Feature Pack for EJB 3.0.
  
  The fix for this APAR is currently targeted for inclusion in
  fixpack 6.1.0.23.  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