Fix (APAR):  PK21504

Status:  Fix

Release:  5.1.1.9,5.1.1.8,5.1.1.7,5.1.1.6,5.1.1.5,5.1.1.4,5.1.1.3,5.1.1.2,5.1.1.1

Operating System:  AIX,HP-UX,Linux,Linux Red Hat - pSeries,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK21504

Byte size of APAR:  6324

Date: 2006-05-02

Abstract:  Inactivity timeout, which is time seconds a cache entry can be remained in cache if not accessed, can be defined for servlets and jsps. However, there is no support for this functi

Description/symptom of problem:  
PK21504 resolves the following problem:

ERROR DESCRIPTION:                                              
Currently the DistributedMap interface does not allow           
to set an inactivity timeout for DistributedMap objects         
that are cached by Dynacache component in WebSphere.            
.                                                               
If your J2EE application requires that                          
a DistributedMap cache object that is cached by                 
Dynacache has to be alive as long as the user regularly         
accesses it, and it should  expire after a preset time          
of inactivity, you have to use a workaround with the            
TIME_TO_LIVE parameter for the put() method of the              
DistributedMap interface.  For example you can                  
work around this limitation by calling "put" after              
every "get" call so that the TIME_TO_LIVE is reset.             
.                                                               
This APAR was open for implementing the inactivity timeout      
parameter for DistributedMap objects                            
that are cached by Dynacache component in WebSphere             
V5.1 & V6.0 releases.                                           

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
All users of Websphere Application Server
using DistributedMap api

PROBLEM DESCRIPTION:
Inactivity timeout, which is time
seconds a cache entry can be remained
in cache if not accessed, can be
defined for servlets and jsps.
However, there is no support for this
function for objects put into cache
via DistributedMap api. This ifix
extends this function to
DistributedMap api as well.

RECOMMENDATION:
None

This ifix extends inactivity timeout support to DistributedMap
api as well.

PROBLEM CONCLUSION:                                             
After applying this ifix developers can define inactivity       
timeout for object put into cache via DistributedMap api.       
                                                                
The fix for this APAR is currently targeted for inclusion       
in cumulative fix 5.1.1.11.                                     
Please refer to the recommended updates page for delivery       
information:                                                    
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   
                                                                


Directions to apply fix:  
NOTE: Choose the:
1) Release the fix applies to
2) The Editions that apply
3) Delete the Editions & Methods that do not apply and this Note

Fix applies to Editions:
Release:
5.0  5.1
___  _x__ Application Server (Express or BASE)
___   x   Enterprise Edition (DD)
___  _x__ Network Deployment (ND)
___  ___ Edge Components
___  ___ Developers Edition
___  ___ Tools
     ___ WebSphere Business Integration Server Foundation (WBISF)

Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
_x_ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

The Update Installer for V5.0 does not have a maintenance directory.
It uses fixpacks and fixes as the location of the unpacked files.

1) Copy the ifix file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (the ifix file which was copied in the maintenance directory).
The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes directory.

7) Install the maintenance package.

8) Restart WebSphere



Directions to remove fix:  
NOTE:
* The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED
* DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED
* YOU MAY REAPPLY ANY REMOVED FIX

Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (ifix file name).

6) UnInstall maintenance package.

7) Restart WebSphere



Directions to re-apply fix:  
1) Shutdown WebSphere.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere.





Additional Information: