PK25682: MEMORY LEAK IN DYNAMIC CACHE PUSHPULLTABLE WHEN PARTNER SERVER SHUTDOWN

6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for HP-UX
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for AIX
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Windows
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Linux
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for i5/OS
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Solaris

APAR status

• Closed as program error.

Error description

• The bug is that the cache's pushPullTable in which the
  location of
  remote cache entries are stored contains stale data.  The data
  becomes
  stale because the server containing the cache content has been
  stopped.
  The replication service does not notify the cache instance that
  the
  server has left.  Therefore those entries for the server that
  left
  are not removed unless a failed request for that cacheID is
  experienced.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere Application Server    *
  *                 version 6 using Dynamic Cache replication    *
  *                 with the push-pull sharing policy.           *
  ****************************************************************
  * PROBLEM DESCRIPTION: Slow memory leak in Dynamic cache       *
  *                      push-pull table when server(s) are      *
  *                      stopped and restarted during cache      *
  *                      load scenarios.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The bug is that the cache's pushPullTable in which the
  location of remote cache entries are stored contains stale
  data.  The data becomes stale because the server containing
  the cache content has been stopped. The replication service
  does not notify the cache instance that the server has left.
  Therefore those entries for the server that left are not
  removed unless a failed request for that cacheID is
  experienced.
  

Problem conclusion

• Replication service propogates the notification of server
  stop to the dynamic cache which in turn cleans up the table.
  
  This fix for this APAR is targeted for inclusion in fixpack
  6.0.2.13 and 6.1.0.1. Please refer to the Recommended Updates
  page to confirm 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:

Modules/Macros

• DRS
  

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