Fix (APAR): PK76168 Status: Fix Release: 6.1.0.19 Operating System: AIX,HP-UX,i5/OS,IBM i,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: PK76168 Byte size of APAR: 64113 Date: 2008-12-05 Abstract: The script (update application) hangs until wsadmin timeout (24 hours) when dmgr process is terminated abnormally. Description/symptom of problem: PK76168 resolves the following problem: ERROR DESCRIPTION:? A problem is seen where a JACL script that updates an EAR file hangs when the Deployment Manager it is connected to is stopped. The wsadmin JACL script never completes. - We will introduce a new system property in wsadmin "com.ibm.ws.scripting.apptimeout" for customers to configure the application install or update timeout value. Customer can specify the system property in a text file with -p or specify it in wsadmin command with -javaoption option. such as: 1. Create a new property or text file, i.e. timeout.prop com.ibm.ws.scripting.apptimeout=1800 (10 mins in milliseconds) wsadmin.bat -conntype RMI -port 2801 -p c:/timout.prop -f c:/bcgapplication.jacl or 2. Specify the system property in wsadmin command with -javaoption wsadmin.bat -conntype RMI -port 2801 -javaoption "-Dcom.ibm.ws.scripting.apptimeout=1800" -f c:/bcgapplication.jacl LOCAL FIX:? Now Local fix at this time. PROBLEM SUMMARY:? USERS AFFECTED: All users of WebSphere Application Server V6.1 and V7.0 PROBLEM DESCRIPTION: The script (update application) hangs until wsadmin timeout (24 hours) when dmgr process is terminated abnormally. RECOMMENDATION: None To workaround the problem, the wsadmin introduces a new system problem com.ibm.ws.scripting.apptimeout for you to configure the application timeout (the default is 24 hours). You can set the application timeout value for test purpose. PROBLEM CONCLUSION:? As stated, the wsadmin introduces a new system property to allow user to change the application max wait time (the default is 24 hours) to a shorter timeout value if any server process is terminated manually and the wsadmin (script) will fail by timeout and throw ConnectionNotAvailableException. The fix for this APAR is currently targeted for inclusion in fixpacks 6.1.0.23 and 7.0.0.3. 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: Fix applies to Editions: Release 6.1 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) _X_ Extended Deployment (XD) Install Fix to: Method: _X_ Both (Application Server and Deployment Manager Nodes) 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.1.0.13 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 /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.ibm.com/support/docview.wss?rs=180&uid=swg21205400 Note that there are two different methods for delivering iFixes, depending on the contents. The fix may be delivered either as a single file with a .pak extension (such as 6.1.0.11-WS-WAS-IFPK12345.pak) or a single file with a .zip extension (such as 6.1.0.11-WS-WAS-IFPK12345.zip) which then contains one or more files with a .pak extension. 1) If your iFix is delivered as a single file with a .pak extension, Copy the .pak file directly to the maintenance directory. If your iFix is delivered as a single file with a .zip extension, unzip the file into 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 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. 8) Please note that in the future, if a Feature Pack is installed or uninstalled, a different set of iFixes will be needed. Use the Update Installer again at that time, with the maintenance directory location where these maintenance packages are stored, to determine the required interim fixes for the new WebSphere and Feature Pack(s) combination. 9) The maintenance packages could have one of a set of names, and these names will help determine which maintenance package you need to install. The APAR name (PKxxxxx) should appear as part of the filename. Between the APAR number and the .pak extension there will be 0 to 2 characters added. The table below indicates the usage of each of the maintenance packages with respect to which Feature Packs, if any, are installed. |.pak File Names |No Feature Packs|EJB3 Only|WebServices Only| Both | |6.1.0.x-WS-WAS-IFPK12345 | X | X | X | X | |6.1.0.x-WS-WAS-IFPK12345C | X | | | | |6.1.0.x-WS-WAS-IFPK12345C 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 (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: The system property timeout value will be set in seconds (not milliseconds) in property file (-p or specify in wsadmin command -javaoption