Fix (APAR):  PQ69610

Status:  Fix

Release:  4.0.5,4.0.4,4.0.3

Operating System:  All

Supersedes Fixes:  PQ67409.

For WebSphere 4.0.3 this EFix must not be used in
conjunction with EFix PQ61550.

CMVC Defect:  PQ69610

Byte size of APAR:  886769

Date: 2003-02-04

Abstract:  Transaction Manager unneccessarily spawns retry thread

Description/symptom of problem:  APAR PQ67409 implements the following changes

The v4.0 transaction manager currently does not handle 
stale connections.  If a network failure occurs with 
in-flight transactions (2PC), the transaction manager is
currently not able to roll back the resource manager.  It
tries once and receives a XAER_RMFAIL.  It then retries the
rollback, but fails with XAER_PROTO.

The solution is to re-instate the stale connection and then
retry.

Also the reconnect to RM logic must throw a TRANSIENT 
Exception if the RM is not yet available on the retry. The
retry will then be done again after a short wait.

APAR PQ69610 Supersedes PQ67409 and implements the same 
logic as well as improving the recovery logic when a 
XAER_RMFAIL is received during an xa_end call to a resource 
manager.


Directions to apply fix:  
1) Create temporary "fix" directory to store the jar file:
 				AIX: /tmp/WebSphere/fix
   Solaris/Linux: /tmp/WebSphere/fix
 		  Windows: c:\temp\WebSphere\fix

2) Copy jar file to the directory

3) Shutdown WebSphere

4) Run the jar file with the following command answering questions/prompts as they appear:
   java -jar <jarfile name>

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 removed, and fix3 re-applied.


1) Change directory to the fix location (<WASHOME>/WebSphere/AppServer/fix/<fix#>).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
	java -jar <backup_fix#>

4) Restart WebSphere


Directions to re-apply fix:  
Follow the instructions for applying a fix.

If the backup files still exist (from the previous fix application), you will be prompted to overwrite.

Answer "yes" at the overwrite prompts.

Additional Information: