Fix (APAR):  JR29661

Status:  Fix

Release:  6.1.0.2,6.1.0.1,6.1,6.0.2.4,6.0.2.3

Operating System:  AIX,HP-UX,i5/OS,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  JR29661

Byte size of APAR:  29163

Date: 2008-09-14

Abstract:  Event Sequencing enabled modules to get stuck messages and stops processing new messages. This also leads into discrepancies between the number of records in the persistantLock man

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

ERROR DESCRIPTION:?                                             
ES enabled module gets stuck messages and stops processing new  
messages. Also leads into discrepancy between number of records 
in persistantLock manager table and number of messages in SCA   
queues.                                                         
                                                                
WPS 6.0.2.3                                                     
WAS 6.0.2.23                                                    
                                                                
SIB Exception APAR # PK67950  is inter-related to this APAR     
and PMR# 78792,057,649 .                                        
                                                                
I have already created another APAR PK68115                     
for this issue which can be                                     
closed as duplicate since i did not notice comp id change in the
original PMR.                                                   

LOCAL FIX:?                                                     
 module stop/start with esAdmin DeleteLocks                     

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server V6.0.2.x, V6.1.0.x,
and V6.1.2.x users with Event Sequencing
modules under heavy transaction load might
experience this problem.

PROBLEM DESCRIPTION:
Event Sequencing enabled modules to
get stuck messages and stops
processing new messages. This also
leads into discrepancies between the
number of records in the persistantLock
manager table and the number of
messages in the Service Ccomponent
Architecture queues.

RECOMMENDATION:
None


As a resultant of SIBus connection dropped exceptions and
TransactionRolledBackExceptions event sequencing tries to
process the events with defalut number of times and hence
there are numerous exceptions thrown into logs like
WorkSubmissionException, SIErrorException. As soon as the
application restarts Event Sequencing process gets restarted
to process the stuck messages.

PROBLEM CONCLUSION:?                                            
Applyin gthis interim fix will resolve the issue.               


Directions to apply fix:  
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 Process Server.

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 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.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

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: