Fix (APAR): PK74220 Status: Fix Release: 6.1.0.17, 6.1.0.19 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,Solaris,Windows Supersedes Fixes: CMVC Defect: PK74220 Byte size of APAR: 1213132 Date: 2008-11-19 Abstract: Maintenance in the area of recovery for the default messaging provider for WebSphere Application Server Description/symptom of problem: PK74220 resolves the following problem: ERROR DESCRIPTION:? This APAR provides interim maintenance for WebSphere Application Server 6.1.0.17 and 6.1.0.19 to allow managed shipment of fixes for specific recovery related problems in the platform messaging component SIBus. LOCAL FIX:? PROBLEM SUMMARY:? USERS AFFECTED: Users of the default messaging provider for WebSphere Application Server V6.1 PROBLEM DESCRIPTION: Maintenance in the area of recovery for the default messaging provider for WebSphere Application Server RECOMMENDATION: Users of the default messaging provider for WebSphere Application Server v6.1 (service integration bus) are recommended to apply this maintenance in combination with fix pack 6.1.0.17 or 6.1.0.19. This includes users of the WebSphere Process Server product, which utilizes service integration buses as a core part of its runtime operation. This maintenance package provides interim fixes for issues that have been encountered in area of recovery. Examples of recovery scenarios are: - Recovery following an unexpected restart of a machine, application server or database. - Recovery following an unexpected network outage. - Recovery following a planned restart of an infrastructure component. PROBLEM CONCLUSION:? The following recovery fixes are included in this APAR: PK68367 Corrects exception destination delivery after database log space is temporarily exhausted. PK60857 Allows cleanup of connections after a failure, when connections are involved in local transactions. PK65259 Prevents deleting a destination with remote queue points from causing messaging engine <-> messaging engine connections to drop with errors PK66797 Prevents deleting a destination with remote queue points from causing a large number of CWSIP0001E messages being logged by application servers PK67067 Prevents a NullPointerException during messaging engine startup after administratively removing messages from a destination that applications are consuming from indirectly (using a remote queue point) PK67950 Improves service integration bus behavior when messages are administratively deleted from a queue while locked by a consuming application PK67998 Prevents message-driven beans from missing messages when applications are consuming messages indirectly (using a remote queue point) PK68303 Allows more than 20 remote queue points to be viewed in the administrative console PK68616 Removes transient SIErrorException failures which could cause SIConnectionDroppedException exceptions. PK68785 Improves reconnection logic for remotely attached message-driven beans after a messaging engine fail-over PK69011 Prevents a failure occurring at a particular point during application connection from causing a deadlock. PK69180 Allows rollbacks to be correctly handled for message-driven beans consuming messages after a messaging engine fail-over PK69047 Improvements in bus behavior in recovery scenarios. PK65439 Provides extra information for investigating a build-up of messages for transfer over an inter-bus link PK60700 Improves reconnection logic for remotely attached message-driven beans after a messaging engine fail-over PK65467 Improves re-delivery logic for queues with a blank exception destination PK61176 Corrects problems that can occur after a rollback happens within the prepare phase of a two-phase commit. PK63099 Ensures the correct system exception destination is used PK63551 Prevents a rollback from affecting indirect message consumption via an intermediate Messaging engine (using a remote queue point) The following prerequisite APARs are also included: PK55950,PK58629,PK59856,PK60008,PK67926,PK65014,PK66053,PK66164 The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.21. 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) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes _X_ 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.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-IFPK12345CE | | X | X | X | |6.1.0.x-WS-WAS-IFPK12345W | X | X | | | |6.1.0.x-WS-WAS-IFPK12345WE | | | X | X | |6.1.0.x-WS-WAS-IFPK12345E | X | | X | | |6.1.0.x-WS-WAS-IFPK12345EE | | X | | X | 10) 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: