Fix (APAR): PK46763 Status: Fix Release: 6.1.0.9,6.1.0.7,6.1.0.5,6.1.0.3,6.1.0.2,6.1.0.13,6.1.0.11,6.1.0.1,6.1,6.0.2.23,6.0.2.21,6.0.2.19,6.0.2.17,6.0.2.15,6.0.2.13,6.0.2.11 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: PK46763 Byte size of APAR: 1079800 Date: 2007-12-20 Abstract: RolloutUpdate restarts the servers before application expansion Description/symptom of problem: PK46763 resolves the following problem: ERROR DESCRIPTION: Rollout Update can cause newly updated applications to not be fully expanded to the InstalledApps directory before proceeding with re-starting the Application Server process. This will cause application exceptions until the Application Server is restarted again. getDistributionStatus() needs to be implemented, so updateAppOnCluster can make use of it. LOCAL FIX: custom script can be used to work around the issue. PROBLEM SUMMARY USERS AFFECTED: IBM WebSphere Application Server users of versions 6.0.2 and 6.1. PROBLEM DESCRIPTION: RolloutUpdate restarts the servers before application expansion RECOMMENDATION: None During application RolloutUpdate operation, an application will be synchronized to the Nodes and expanded to its destination directory (default, installedApps directory). The application expansion will be executed in a seperate thread, as a background process. But, RolloutUpdate operation starts the cluster member servers before the application binaries are completely expanded to its directories. Because the applications are still being expanded, the application fails to start during server startup. RolloutUpdate operation should delay the server startup until the application binaries are expanded to their directories. PROBLEM CONCLUSION: The fix will delay the server startup until the application is expanded to its destination. By default, the fix will wait for one minute, for appliction expansion; but, the wait time is configurable through the "com.ibm.websphere.management.application.updatesync. appExpansionTimeout" (all on one line) custom property. . The wait time defined through this property should be the maximum time taken for application expansion in a Node. The property need to be defined as a System property in Dmgr JVM. The fix for this APAR is currently targeted for inclusion in fix packs 6.0.2.25 and 6.1.0.15. 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.0 _Y_ Network Deployment (ND) Install Fix to: Method: _Y_ 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.0.2.5 or newer of the Update Installer. 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-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy PKxxxxx.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.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 (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: For WAS versions 6.0.2.11 to 6.0.2.17, use the file 6.0.2.17-WS-WAS-IFPK46763.pak For WAS versions 6.0.2.19 to 6.0.2.23, use the file 6.0.2.23-WS-WAS-IFPK46763.pak For WAS versions 6.1.0.0 to 6.1.0.13, use the file 6.1.0.13-WS-WAS-IFPK46763.pak