Fix (APAR):  JR24901

Status:  Fix

Release:  6.0.1.3

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  29605

Date: 2006-12-01

Abstract:  Failed Event Manager (FEM) application cannot start, and it can not look at the detail info of the failed event that are created on 601 WPS.

Description/symptom of problem:  
JR24901 resolves the following problem:

ERROR DESCRIPTION:                                              
Failed event generated from WPS 6011 can not be resubmit after  
upgrade WPS to 6012.                                            
                                                                
Here is the exception,                                          
[9/26/06 13:41:10:531 IST] 00000067 RecoveryMgr   E             
com.ibm.wbiserver.management.FailedEventManagerMBean            
getFailedEventWithParameters() CWRCV0027E: Errors encountered   
while                                                           
getting message details for a failed event with the message ID  
372DABD638E45A5B_58509495.                                      
[9/26/06 13:41:10:656 IST] 00000067 MBeanHelper   E   Could not 
invoke                                                          
an operation on object:                                         
WebSphere:cell=integrationswNode01Cell,version=6.0.2.9,name=Fail
edEventM                                                        
anager,mbeanIdentifier=cells/integrationswNode01Cell/nodes/integ
rationsw                                                        
Node01/servers/server1/server.xml#CustomService_1153734606812,ty
pe=Faile                                                        
dEventManager,node=integrationswNode01,process=server1 because  
of an                                                           
mbean exception:                                                
com.ibm.wbiserver.manualrecovery.exceptions.FailedEventDataExcep
tion:                                                           
java.io.InvalidClassException:                                  
com.ibm.wbiserver.manualrecovery.RecoveryDataContainer; local   
class                                                           
incompatible: stream classdesc serialVersionUID =               
2797451871400103508,                                            
local class serialVersionUID = 5910926683441443642              

LOCAL FIX:                                                      
N/A                                                             

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.1.x users
who use Failed Event Manager (FEM)
application 6013 WPS cluster.

PROBLEM DESCRIPTION:
Failed Event Manager (FEM) application
cannot start, and it can not look at
the detail info of the failed event
that are created on 601 WPS.

RECOMMENDATION:
None

On 6013 WPS cluster, FEM application cannot start. To solve
it, when apply 6013 fix pack, we need to exclude PK29634 and
IF353793. Then FEM application can start successfully. We can
put a flash out for the customers to remove the 2 ifixes.

On 6013 WPS, FEM cannot look at the detail info of the failed
event that are created on 601 WPS. To solve it, we need apply
WPS iFix pak for JR24901 on WPS 6013, then it works fine.

PROBLEM CONCLUSION:                                             
Issues on 6013 WPS cluster,                                     
1) FEM application cannot start                                 
2) FEM cannot look at the detail info of the failed             
event that are created on 601 WPS                               
can be resolved by excluding PK29634 and IF353793 when apply    
6013 fix pack, and applying WPS iFix pak for JR24901 on WPS6013.


Directions to apply fix:  
Before applying the iFix ensure that WebSphere Process Server 6.0.1 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) 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) 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) 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: