Fix (APAR): JR27454 Status: Fix Release: 6.0.2.2 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 427353 Date: 2007-10-11 Abstract: Cannot resubmit failed events from Failed Event Manager. Description/symptom of problem: JR27454 resolves the following problem: ERROR DESCRIPTION: Illegal State Exception is received when resubmitting events that have failed. This appears to be due to the data and specific Year types not being serialized propely. Test fix was provided and it working well. LOCAL FIX: none PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server 6.0.2 users. PROBLEM DESCRIPTION: Cannot resubmit failed events from Failed Event Manager. RECOMMENDATION: None The problem occurs when we lose Business Object item's type info (BaseType, ItemType, MemberTypes) during serialization of the Business Object. Getting the Business Object definition information from the relevant application's registry before resubmit failed events resolves the problem. PROBLEM CONCLUSION: Applying this interim fix resolves the problem. Directions to apply fix: Before applying the iFix ensure that WebSphere Process Server 6.0.2.2 is installed on the system. Also download and follow Update Installer installation instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) Copy the pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere Process Server. 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) Run the UpdateInstaller and follow the prompts. 4) For stand-along server, running this command from each profiles' bin directory. wsadmin -conntype none -f [WPS Root]\util\Recovery\RecoveryAppUpgrade.jacl 5) For Cluster, running this command from each deployment manager (DMGR) profiles' bin directory. wsadmin -conntype none -f [WPS Root]\util\Recovery\RecoveryAppUpgrade.jacl 4) Restart WebSphere Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH 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) Backup [WPS Root]\util\Recovery\RecoveryAppUpgrade.jacl first 3) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 4) Restore the RecoveryAppUpgrade.jacl to [WPS Root]\util\Recovery\ 5) For stand-along server, running this command from each profiles' bin directory. wsadmin -conntype none -f [WPS Root]\util\Recovery\RecoveryAppUpgrade.jacl 6) For Cluster, running this command from each deployment manager (DMGR) profiles' bin directory. wsadmin -conntype none -f [WPS Root]\util\Recovery\RecoveryAppUpgrade.jacl 7) Delete [WPS Root]\util\Recovery\RecoveryAppUpgrade.jacl 8) 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) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 3) Restart WebSphere Process Server Additional Information: