Fix (APAR): PK66889 Status: Fix Release: 6.1.0.2,6.1.0.1 Operating System: AIX,HP-UX,Linux,Solaris,Windows,z/OS Supersedes Fixes: PK65856 CMVC Defect: PK66889 Byte size of APAR: 181747 Date: 2008-06-17 Abstract: After an application edition rollout, Http requests are returned with Http response code of 503. Description/symptom of problem: PK66889 resolves the following problem: ERROR DESCRIPTION: Useing the Application edition feature of WebSphere Extended Deployment, during the role out of a new edition of an applicationor putting an edition into validation mode, instead of queuing the request or routing the request to the new edition as expected, the On Demand Router returns a Http 1.1 503 response. LOCAL FIX: N/A PROBLEM SUMMARY USERS AFFECTED: All users of WebSphere Extended Deployment using the On Demand Router. PROBLEM DESCRIPTION: After an application edition rollout, Http requests are returned with Http response code of 503. RECOMMENDATION: None When an application edition is being rolled out, existing Http session requests need to finish up on the old edition. After this was done, there were additional requests being sent to the older edition, but needed to be routed to the new edition. This resulted in a 503 Http response code, because the application server of the older edition was not in a started state. PROBLEM CONCLUSION: The code was fixed to route requests properly and the fix was made available for the 6.1 release. The fix will be included in Service Pack 6.1.0.3 for WebSphere Extended Deployment. Directions to apply fix: Install Fix to: _X_ Application Server Nodes __ Deployment Manager Nodes __ Both NOTE: The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. Also, you should be logged in with the same authority level when unpacking a fix, fix pack or refresh pack. DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX. The Fix 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. Customers must 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 /updateinstaller/version.txt. 1) Copy 6.1.0.1-WS-WXD-IFPK66889.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.1.0.1-WS-WXD-IFPK66889.pak 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. NOTE: 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.1.0.1-WS-WXD-IFPK66889.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: