Fix (APAR): PK67161 Status: Fix Release: 5.1.1.9,5.1.1.8,5.1.1.7,5.1.1.6,5.1.1.5,5.1.1.4,5.1.1.3,5.1.1.2,5.1.1.17,5.1.1.16,5.1.1.15,5.1.1.14,5.1.1.13,5.1.1.12,5.1.1.11,5.1.1.10,5.1.1.1,5.1.1 Operating System: AIX,HP-UX,Linux,Linux pSeries,Linux zSeries,Solaris,Windows Supersedes Fixes: none CMVC Defect: PK67161 Byte size of APAR: between 705884 and 1475153 bytes, depending on platform Date: 2008-07-21 Abstract: Client side errors were incorrectly marking application servers down. Description/symptom of problem: PK67161 resolves the following problem: ERROR DESCRIPTION: 1) Plugin is marking servers down when a read from the client fails which is causing excessive errors for the users of IBM® WebSphere plugin. Fixes are also available for versions on 6.0.2 and 6.1 at: http://www.ibm.com/support/docview.wss?rs=180&uid=swg24019451 LOCAL FIX: None PROBLEM SUMMARY USERS AFFECTED: All users of the Web server plug-in component of IBM WebSphere Application Server V5.1. PROBLEM DESCRIPTION: Plugin is marking servers down when a read from the client fails which is causing excessive errors for the user. RECOMMENDATION: If servers are being marked down from client side errors, install this fix. PROBLEM CONCLUSION: Changes have been made in this interim fix to prevent client side errors from incorrectly marking servers down.. 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 6.0 __ Application Server (Express or BASE) __ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) Install Fix to: Method: __ 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. * 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 /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. WAS51X Selecting the correct interim fix for PK67161 The interim fix for PK67161 is applicable to seven different 32bit platforms: AixPPC32 for AIX on PowerPC, HpuxPaRISC for HPUX on PaRISC, LinuxPPC32 for Linux on PowerPC, LinuxS390 for Linux on S/390, LinuxX32 for Linux on x86, SolarisSparc for Solaris on Sparc, and WinX32 for Windows on x86. Download the package that matches the target platform and install it following the directions below. Installation The manual procedure for installing this interim fix includes locating, backing up, and replacing one or more of these existing files: mod_was_ap20_http IBM HTTP Server V2.0 mod_ibm_app_server_http IBM HTTP Server V1.3 mod_app_server_http Apache V1.3 mod_app_server_http_eapi Apache V1.3 with Open SSL ns_41_http iPlanet V4.0 and V6.0 for Microsoft® Windows® libns_41_http iPlanet V4.0 and V6.0 for UNIX® domino5_http Domino® V5.0 and Domino V6.0 for Microsoft Windows libdomino5_http Domino V5.0 and Domino V6.0 for UNIX, except Solaris libdomino6_http Domino V6.0 for Solaris iisWASPlugin_http Internet Information Services V4.0, V5.0 and V6.0 Note: The WebSphere Application Server version tracking files are not updated using this manual installation process. Steps to install WebSphere plugin interim fix binaries for local webservers: 1. Stop the webserver 2. Use UpdateInstaller to install the fixpack 3. Restart the webserver Steps to install WebSphere plugin interim fix binaries for remote webservers: 1 Stop the webserver 2 Navigate to the installation directory of the plugin 3 Change into the /bin directory 4 From the list above, determine which files are applicable in the installation 5 Back up all applicable files 6 Unzip the correct interim fix 7 Search the unzipped files for update.jar 8 Unzip update.jar 9 Copy each applicable file from the unzipped file to the /bin directory 10 Restart the webserver For a more thorough description, please reference this link: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24007227 Uninstallation Steps to uninstall WebSphere plugin interim fix binaries for local webservers: 1. Stop the webserver 2. Use UpdateInstaller to uninstall the fixpack 3. Restart the webserver Steps to uninstall WebSphere plugin interim fix binaries for remote webservers: 1 Stop the webserver 2 Navigate to the installation directory of the plugin 3 Change into the /bin directory 4 Remove each file that was installed in the installation procedure 5 Restore each of the previously backed up files using the original file 6 Restart the webserver WAS602 Selecting the correct interim fix for PK67161 The interim fix for PK67161 is applicable to fifteen different 32bit or 64bit platforms: AixPPC32 for AIX on PowerPC, AixPPC64 for AIX on 64bit PowerPC, HpuxIA64 for HPUX on 64bit Itanium, HpuxPaRISC for HPUX on PaRISC, LinuxIA64 for Linux on 64bit Itanium, LinuxPPC32 for Linux on PowerPC, LinuxPPC64 for Linux on 64bit PowerPC, LinuxS390 for Linux on S/390, LinuxX32 for Linux on x86, LinuxX64 for Linux on 64bit x86, SolarisSparc for Solaris on Sparc, SolarisSparc64 for Solaris on 64bit x86, WinIA64 for Windows on 64bit Itanium, WinX32 for Windows on x86, and WinX64 for Windows on 64bit x86. If the target system is a 32bit architecture, select the package that includes the characters "32" and the appropriate operating system name. Three exceptions to this are HpuxPaRISC, LinuxS390, or SolarisSparc which do not contain the characters "32," but are 32bit interim fixes. If the target system is a 64bit architecture, first it must be determined if the actual installation on the target machine is 32bit or 64bit. Some webservers on 64bit architectures are actually 32bit binaries. To determine this, using a file manager or command window, navigate to the installation root of the plugin. Change into the /bin subdirectory and note if there are any binaries installed. If so, this is a 32bit installation and the appropriate 32bit interim fix package should be downloaded. If no binaries are installed in this directory, but it contains two subdirectories, 32bits and 64bits, then the appropriate 64bit interim fix package should be downloaded. Download the package that matches the target platform and bit size (32 or 64), and install it following the directions below. Installation Steps to install the interim fix: 1. Stop the webserver 2. Download the appropriate interim fix 3. Use the UpdateInstaller tool to install the interim fix 4. Restart the webserver For a more thorough explanation, reference this link: http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&dc=DA490&dc=DA4A10&dc=DB520&dc=DA4A30&dc=DB530&dc=DA480&dc=D700&dc=DA4A20&dc=DB560&dc=DA440&dc=DA460&dc=DA430&dc=DA470&dc=DB550&dc=D600&dc=DB600&dc=DA420&dc=DA500&dc=DA410&dc=DB540&dc=DB700&dc=DA400&dc=DB510&q1=update+installer&uid=swg21170965&loc=en_US&cs=utf-8&lang=en Uninstallation Steps to uninstall the interim fix: 1. Stop the webserver 2. Use the UpdateInstaller tool to uninstall the interim fix 3. Restart the webserver WAS61 Selecting the correct interim fix for PK67161 The interim fix for PK67161 is applicable to fifteen different 32bit or 64bit platforms: AixPPC32 for AIX on PowerPC, AixPPC64 for AIX on 64bit PowerPC, HpuxIA64 for HPUX on 64bit Itanium, HpuxPaRISC for HPUX on PaRISC, LinuxPPC32 for Linux on PowerPC, LinuxPPC64 for Linux on 64bit PowerPC, LinuxS390 for Linux on S/390, LinuxS39064 for Linux on 64bit S/390, LinuxX32 for Linux on x86, LinuxX64 for Linux on 64bit x86, SolarisSparc for Solaris on Sparc, SolarisSparc64 for Solaris on 64bit Sparc, SolarisX64 for Solaris on 64bit x86, WinX32 for Windows on x86, and WinX64 for Windows on 64bit x86. If the target system is a 32bit architecture, select the package that includes the characters "32" and the appropriate operating system name. Three exceptions to this are HpuxPaRISC, LinuxS390, or SolarisSparc which do not contain the characters "32," but are 32bit interim fixes. If the target system is a 64bit architecture, first it must be determined if the actual installation on the target machine is 32bit or 64bit. Some webservers on 64bit architectures are actually 32bit binaries. To determine this, using a file manager or command window, navigate to the installation root of the plugin. Change into the /bin subdirectory and note if there are any binaries installed. If so, this is a 32bit installation and the appropriate 32bit interim fix package should be downloaded. If no binaries are installed in this directory, but it contains two subdirectories, 32bits and 64bits, then the appropriate 64bit interim fix package should be downloaded. Download the package that matches the target platform and bit size (32 or 64), and install it following the directions below. Installation Steps to install the interim fix: 1. Stop the webserver 2. Download the appropriate interim fix 3. Use the UpdateInstaller tool to install the interim fix 4. Restart the webserver Additional Information: For a more thorough explanation, reference this link: http://www.ibm.com/support/docview.wss?rs=180&context=SSEQTP&dc=DA490&dc=DA4A10&dc=DB520&dc=DA4A30&dc=DB530&dc=DA480&dc=D700&dc=DA4A20&dc=DB560&dc=DA440&dc=DA460&dc=DA430&dc=DA470&dc=DB550&dc=D600&dc=DB600&dc=DA420&dc=DA500&dc=DA410&dc=DB540&dc=DB700&dc=DA400&dc=DB510&q1=update+installer&uid=swg21170965&loc=en_US&cs=utf-8&lang=en Uninstallation Steps to uninstall the interim fix: 1. Stop the webserver 2. Use the UpdateInstaller tool to uninstall the interim fix 3. Restart the webserver