Fix (APAR):  PM69146

Status:  Fix

Release:  7.1.1.1

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  PM57833;PM57811;PM59011;PM59456;59482;PM59004;PM59642;PM60480;PM62770;PM63607;PM64258;PM64821;PM63415;PM66345;PM66465;PM65523;PM67240;PM67580;PM68535;PM60238;PM61170;PM68654;PM63208;PM68689;PM68769

CMVC Defect:  PM69146

Byte size of APAR:  75341350

Date: 2012-08-22

Abstract:  If you use a key with a high rate of contention, the lock state can become corrupted and cause LockTimeoutException errors.

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

ERROR DESCRIPTION:                                              
TheLockTimeoutException exception occurs even though the lock   
was granted. Therefore, the lock is not released and future     
requests for the lock fail.                                     

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
 All users of WebSphere eXtreme Scale who
use locking.

PROBLEM DESCRIPTION:
If you use a key with a high rate of
contention, the lock state can become
corrupted and cause
LockTimeoutException errors.

RECOMMENDATION:
None

A problem was identified where a lock request was reported as
failed; however, the lock was granted shortly after the
request. The code was updated to do an additional check to
determine whether the lock request was granted after getting
the appropriate monitor.

PROBLEM CONCLUSION:                                             
An interim fix is available for this problem.                   


Directions to apply fix:  
Fix applies to Editions: 7.1.1.1
Release:
     _X__ WebSphere eXtreme Scale

Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
_X_ Both
_X_ WebSphere eXtreme Scale standalone
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 7.1.1.1-WS-WXS-IFPM69146.pak 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 (PKxxxxx.jar 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 Application Server.
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 (P7.1.1.1-WS-WXS-IFPM69146.pak).

6) UnInstall maintenance package.

7) Restart WebSphere

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

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere Application Server.



Additional Information: