Fix (APAR):  JR30708

Status:  Fix

Release:  6.1.2,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:  xxxxxx

Byte size of APAR:  224060

Date: 2008-11-20

Abstract:  Service Component Architecture (SCA) message driven bean could encounter deadlock condition.

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

ERROR DESCRIPTION:?                                             
Fix JR27047 changes the logic in SCA such that any message      
received by an SCA message driven bean is held until either a)  
1/2 times the transaction timeout has elapsed or b) all         
applications have completed starting. This logic can cause a    
deadlock condition as an in flight transaction is held with a   
'wait' condition which may take some time to release.           
                                                                
The proposed update is to change the server logic so that it    
does not hold a running transaction to wait on a condition, but 
instead prevents the transaction from being created in the first
place until such a time as it can be processed successfully.    
This requires that the JCA endpoints not be activated until all 
applications have completed starting.                           

LOCAL FIX:?                                                     
NA                                                              

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server and WebSphere
Enterprise Service Bus 6.0.2.x, 6.1.0.x,
and 6.1.2.x users.

PROBLEM DESCRIPTION:
Service Component Architecture (SCA)
message driven bean could encounter
deadlock condition.

RECOMMENDATION:
None

Service Component Architecture (SCA) message driven bean could
encounter deadlock condition as an in flight transaction is
held with a 'wait' condition which may take some time to
release. This issue is involved by JR27047.

PROBLEM CONCLUSION:?                                            
Fixed this issue by remove JR27047. The WAS fix PK73716 will    
fix what JR27047 fixed with a better way                        


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: