Fix (APAR):             PQ93714

Status:                 Fix

Release:                5.1.0

Operating System:       All

Supersedes Fixes:       

Pre-requisite Fixes:    

CMVC Defect:            PQ93714

Byte size of APAR:      6997

Date:                   2004-08-06

Abstract:               Timeout Causes The Current Transaction To Rollback

Description/symptom of problem:
When a transaction is started on a server and is re-imported onto the same server,
the transaction is not recognised as being known, so a new transaction is created.
This type of flow is generally known as a callback.
If the original transaction performed any work against an XA resource, and the
re-imported transaction attempts to access the same XA resource, deadlock will
occur. Depending on the level of the XA resource, this deadlock may either be
detected and an error generated, or a transaction timeout may occur.
This fix changes the TXServerInterceptor class so that the server identifies
the transaction as one it recognises when the transaction is re-imported.

Directions to apply fix:

NOTE:  YOU MUST FIRST DOWNLOAD THE FIX INSTALLER TOOL IN ORDER TO INSTALL A FIX.
       The Fix Installer can be downloaded from the following link:
       http://www-3.ibm.com/software/webservers/appserv/support/index.html

1) Create temporary "fix" directory to store the jar file:
          UNIX: /tmp/WebSphere/fix
          Windows: c:\temp\WebSphere\fix

2) Copy jar file to the directory

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

4) Follow the Fix installation instructions that are packaged with the Fix Installer on how to install the Fix.

5) Restart WebSphere

6) The temp directory may be removed but the jar file should be saved.  Do not remove
   any files created and stored in the <WASHOME>/WebSphere/AppServer/fix/<fix> directories.
   These files are required if a fix is to be removed.


Directions to remove fix:
NOTE:  FIXES MUST BE REMOVED IN THE ORDER 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, fix2

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) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere


Additional Information: