Fix (APAR): PK71156 Status: Fix Release: 6.0.2.29,6.0.2.27 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,Solaris,Windows Supersedes Fixes: CMVC Defect: PK71156 Byte size of APAR: 590266 Date: 2008-08-28 Abstract: Maintenance in the area of recovery for the default messaging provider for WebSphere Application Server Description/symptom of problem: PK71156 resolves the following problem: ERROR DESCRIPTION:? This APAR provides interim maintenance for WebSphere Application Server 6.0.2.27 and 6.0.2.29 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.0 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.0 (service integration bus) are recommended to apply this maintenance in combination with fix pack 6.0.2.27 or 6.0.2.29. 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, with WebSphere Application Server 6.0.2.27 and 6.0.2.29. 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. The following recovery fixes are included in this APAR: PK60700 Improves reconnection logic for remotely attached message-driven beans after a messaging engine fail-over PK61972 Improves messaging engine <-> messaging engine connection restart logic PK63551 Prevents a rollback from affecting indirect message consumption via an intermediate messaging engine (using a remote queue point) 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) PK67998 Prevents message-driven beans from missing messages when applications are consuming messages indirectly (using a remote queue point) PK68785 Improves reconnection logic for remotely attached message-driven beans after a messaging engine fail-over PK63099 Ensures the correct system exception destination is used PK67950 Improves service integration bus behavior when messages are administratively deleted from a queue while locked by a consuming application PK69180 Allows rollbacks to be correctly handled for message-driven beans consuming messages after a messaging engine fail-over PK65467 Improves redelivery logic for queues with a blank exception destination PK68616 Removes transient SIErrorException failures which could cause SIConnectionDroppedException exceptions. These could occur when consuming messages indirectly (using a remote queue point) PK68303 Allows more than 20 remote queue points to be viewed in the administrative console The following prerequisite fixes are also included: PK57739 Corrects calculation of publication point depth PK62569 Allows publication point depth to be queried in wsadmin PK60008 Updates an interface provided by the service integration bus for WebSphere Extended Deployment (XD) PROBLEM CONCLUSION:? The fix for this APAR is currently targeted for inclusion in fixpack 6.0.2.31. 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 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.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. After installing the fix package, and before starting any application servers or the deployment manager, run the following command from the deployment manager profile (or the application server profile in a stand-alone server environment): UNIX: /bin/iscdeploy.sh -restore Windows: \bin\iscdeploy.bat -restore This is required to enable the fix for PK68303 in the administrative console. 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.