Fix (APAR):  PK71345

Status:  Fix

Release:  7.0

Operating System:  AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  545923

Byte size of APAR:  24997

Date: 2008-11-17

Abstract:  A memory leak might occur when WS-Transactions is used in conjunction with web services applications.

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

ERROR DESCRIPTION:?                                             
Memory leak when WS-Transactions is used under stress           

LOCAL FIX:?                                                     

PROBLEM SUMMARY:?

USERS AFFECTED:
 Users that have web services applications
that use WS-Transactions.

PROBLEM DESCRIPTION:
A memory leak might occur when
WS-Transactions is used in
conjunction with web services
applications.

RECOMMENDATION:
None

In certain situations where the WS-Transactions function is
being used in conjunction with web services applications, a
memory leak can occur.   The leak is fairly small, but might
become noticeable if the app server continues to run for
several days in a high-stress situation.   On the z/OS
platform, this memory leak occurs in the native memory heap.
On other platforms, it occurs in the Java memory heap.

PROBLEM CONCLUSION:?                                            
                                                                
                                                                
The fix for this APAR is currently targeted for inclusion in    
fixpack 6.1.0.21 and 7.0.0.1.  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 7.0
__ Application Server (Express or Base)
__ Network Deployment (ND)
__ Edge Components
__ Developer

Install Fix to all WebSphere installations unless special instructions are included below.

Special Instructions: None

NOTE:
The user must:
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V7.0.0.0 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. This can be checked by reviewing the level of the Update Installer in file <UPDI_root>/updateinstaller/version.txt.

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

1) The fix is delivered as a single file with a .pak extension (such as 7.0.0.1-WS-WAS-IFPK12345.pak). Copy the .pak file directly to the maintenance directory, <UPDI_root>/maintenance. 

2) Shutdown WebSphere

3) For IBM i users, use the update command to install and uninstall the interim fix.  The IBM Information Center can provide additional details, if needed, on the use of this command.
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=rins_update.

For non-IBM i users, launch the Update Installer and click the Next button on the Welcome page.

4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button.

5) Select the "Install maintenance package" operation and click the Next button.

6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button.

7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step.
The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed.  
Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package.
To determine why some maintenance packages have been identified as not applicable, see description in log found in <UPDI_root>/logs/tmp*/updatelogs.txt

8) For all platforms except Windows. In pre-install summary panel, use the "verify permission" feature to verify the user has permissions to apply updates to files associated with the selected maintenance.  Correct any file permissions before clicking next to start the install.

9) Restart WebSphere




Directions to remove fix:  

1) Shutdown WebSphere

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) Select name of the maintenance package to uninstall (PKxxxxx.pak).

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: