Fix (APAR): IZ26471 Status: Fix Product: WBI Release: 6.1.2.0 Operating System: All operating systems Supersedes Fixes: Pre-requisite Fixes: Exclusive-requisite Fixes: CMVC Defect: IZ26471 Byte size of APAR: 32820 Date: 2008-07-29 Abstract: Invoke activities may remain in state Running under high stress. Description/symptom of problem: If under high stress situations the processing of an asynchronous reply for an invoke activity fails, this activity may remain in state running. This prevent the process instance from continuing navigation. NOTE: This interim fix is applicable to both a full WPS installation as well as a WPS client installation. Directions to apply fix: 1) Copy pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Follow the Fix installation instructions that are packaged with the Fix Installer on how to install the Fix. 4) Restart WebSphere Directions to remove fix: 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, then fix2 may be removed 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Additional Information: