Fix (APAR):  JR25525

Status:  Fix

Release:  6.0.2

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  7297

Date: 2006-12-14

Abstract:  SCA does not handle transaction correctly during async response.

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

ERROR DESCRIPTION:                                              
Scenario is one that involves a JMS Export and a Long running   
process.                                                        
When the long running process initiates a response to be sent   
back to                                                         
the caller via the JMS Export, SCA transaction handler suspended
the                                                             
transaction context of the BPC component and forced the JMS     
Export to                                                       
be executed in a Local Transaction.                             
                                                                
This introduces potential risks that multiple responses could   
result                                                          
which compromises the integrity of the system. Such problem     
would only                                                      
occur if one or more of the transactions involved decided to    
rollback.                                                       

LOCAL FIX:                                                      
None                                                            

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.1.x users

PROBLEM DESCRIPTION:
SCA does not handle transaction
correctly during async response.

RECOMMENDATION:
None

Scenario is one that involves a JMS Export and a Long running
process. When the long running process initiates a response to
be sent back to the caller via the JMS Export, SCA transaction
handler suspended the transaction context of the BPC component
and forced the JMS Export to be executed in a Local
Transaction.

This introduces potential risks that multiple responses could
result which compromises the integrity of the system. Such
problem would only occur if one or more of the transactions
involved decided to rollback.

PROBLEM CONCLUSION:                                             
This fix fixes the problem described above.                     


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: