Fix (APAR):  JR29600

Status:  Fix

Release:  6.1.2

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  28713

Date: 2008-08-21

Abstract:  Under certain conditions a timeout or deadlock can occur when invoking a service asynchronously with default reference tx qualifier.

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

ERROR DESCRIPTION:?                                             
Enhance SCA to detect runtime deadlock caused by tx default     

LOCAL FIX:?                                                     
None                                                            

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server v6.1.2 Users.

PROBLEM DESCRIPTION:
Under certain conditions a timeout or
deadlock can occur when invoking a
service asynchronously with default
reference tx qualifier.

RECOMMENDATION:
None

In WebSphere Integration Developer(WID) 612, default reference
tx qualifier has been changed from "Call" to "Commit". When
this change, modules developed in the WID 612 (or higher
version) may run into a "deadlock" situation if an
invokeAsync() and invokeResponse() is called on the same
thread and same the transaction context. This is more likely
in the usage of a Mediation Flow Component where the mediation
flow could potentially make an outbound request and blocked for
an asynchronous response within the same transaction context.

PROBLEM CONCLUSION:?                                            


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: