PK41845: DISTRIBUTEDMAP GLOBAL TIMETOLIVE ( DISTMAP.SETTIMETOLIVE() ) NOT EXPIRING CACHE ENTRIES.

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
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

• DistributedMap global TimeToLive ( distMap.setTimeToLive() ) not
  expiring cache entries.
  
  The DistributedMap.put(key, value) does not use global
  timeToLive.
  It is set to no timeout which causes the entry never expired.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM WebSphere Application Server versions    *
  *                 6.0.2 and 6.1 users using DistributedMap     *
  ****************************************************************
  * PROBLEM DESCRIPTION: DistributedMap global TimeToLive is     *
  *                      not working.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  DistributedMap.setTimeToLive() API to set global TimeToLive
  does not work. Using the DistributedMap.put(key, value)
  the cache entries never expire even though this gobal
  TimeToLive API is used.
  

Problem conclusion

• After setting Global TimeToLive, the code was modified to pass
  this variable when performing DistributedMap.put(key, value).
  The cache entries will expire according to Gobal TimeToLive
  variable.
  
  The fix for this APAR is currently targeted for inclusion
  in fixpacks 6.0.2.23 and 6.1.0.11.
  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:

Modules/Macros

• DYNACACH
  

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

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