PK86876: OUT OF MEMORY PROBLEMS CAUSED BY SESSION ENTRIES NOT BEING DELETED.

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

• CSIv2 Session entries were not getting cleaned up, new sessions
  being created. Since default garbage collection runs after 15-20
  minutes there are too many old sessions taking up memory. Out of
  Memory errors resulted.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application Server
  ****************************************************************
  * PROBLEM DESCRIPTION: In some customer situations CSIv2       *
  *                      Session entries are not garbage         *
  *                      collected quickly enough, causing       *
  *                      out of memory problems                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In some customer situations, CSIv2 session entries build up
  quickly and cause out of memory problems. The garbage
  collector cannot be tweaked easily to clean up the expired
  CSIv2 session entries. With this fix a CSIv2 session cache
  limit can be set using a custom property. This can be used to
  limit the size of the cache and delete the expired entries more
  frequently.
  

Problem conclusion

• This fix introduces a CSIv2 session cache limit that can set
  using a custom property. This helps in preventing out of
  memory problems with CSIv2 sessions.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.0.2.39 and 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

• 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