Fix (APAR):  PK37699

Status:  Fix

Release:  6.0.2

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

Supersedes Fixes:  

CMVC Defect:

Byte size of APAR:  35713

Date: 2007-03-08

Abstract:  Support for specifying -X and -XX JVM parameters for the underlying JVM for the WsAdmin Ant task to prevent OutOfMemoryExceptions when run on the HP-UX Itanium platform.

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

ERROR DESCRIPTION:                                              
Support for specifying -X and -XX JVM parameters for the underlying JVM for the WsAdmin Ant task to prevent OutOfMemoryExceptions when run on the HP-UX Itanium platform.

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY
When running the WsAdmin Ant task via ws_ant an OutOfMemoryException on the HP-UX Itanium platform.

USERS AFFECTED:
WebSphere Application Server ws_ant users of version 6.0.2.

PROBLEM DESCRIPTION:
An OutOfMemoryException can occur when running the WsAdmin Ant task on the HP-UX Itanium platform.


RECOMMENDATION:
None


PROBLEM CONCLUSION:                                             
The fix will allow -X and -XX JVM parameters to be set on the underlying JVM for the WsAdmin Ant task to prevent the OutOfMemoryExceptions from occurring.
                                                                
The fix for this APAR is currently targeted for inclusion in fixpack 6.0.2.19.  
                                           
Please refer to the recommended updates page for delivery information:
http://www.ibm.com/support/docview.wss?uid=swg27004980

Directions to apply fix:  

Fix applies to Editions:
Release 6.0
_y_ Application Server (Express or BASE)
_y_ Network Deployment (ND)

Install Fix to:
Method:
_y_ Application Server Nodes
_y_ Deployment Manager Nodes
_y_ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

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

For detailed instructions to Extract the Update Installer see the following Technote:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400

1) Copy 6.0.2-WS-WAS-IFPK37699.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 (6.0.2-WS-WAS-IFPK37699.pak file which was copied in the maintenance 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 (6.0.2-WS-WAS-IFPK37699.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: