eFix (APAR): PQ67409

Status:      E-Fix

For Release: WebSphere 4.0.4 4.0.5

For Edition: WebSphere AE

For Container Types: All

For Operating System:

Supersedes eFixes: PQ65676

Pre-requisite eFixes: None.

Date: 17th October 2002

Title: JTS Transaction Manager must detect stale connections & retry on new
       connections.

Abstract:
        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 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.

Directions to apply eFix:

1) Create temporary "efix" directory to store the zip/tar file:
         Windows: c:\temp\WebSphere\efix

2) Copy zip/tar file to the directory

3) Unzip/untar the file

4) Shutdown WebSphere

5) Run the jar file with the following command answering questions/prompts as they appear:
   java -jar PQ67409-4.0.4.jar

6) Restart WebSphere

7) The temp directory may be removed but the zip/tar file should be saved.  Do not remove
   any files created and stored in the <WASHOME>/WebSphere/AppServer/efix/PQ67409 directories.
   These files are required if an efix is to be removed.



Directions to remove an efix:

NOTE:  EFIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE AN EFIX UNLESS
       ALL EFIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED EFIX.

Example:  If your system has efix1, efix2, and efix3 applied in that order and efix2 is to be
          removed, efix3 must be removed first, efix2 removed, and efix3 re-applied.


1) Change directory to the efix location (<WASHOME>/WebSphere/AppServer/efix/PQ67409).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
   java -jar PQ67409-4.0.4_backup.jar

4) Restart WebSphere



Directions to re-apply an efix:

Follow the instructions for applying an efix.  If the backup files still exist (from the
previous efix application), you will be prompted to overwrite.  Answer "yes" at the overwrite
prompts.


Trouble shooting
--------------------------------------------------------------------------------------
o  If an efix complains about the container type and you are sure it should match, contact
   WebSphere L2 Support for assistance with the -SkipContainerCheck option to the efix jar.

o  If the efix complains about the version of XML parser, move the file
   $WASROOT/jre/lib/ext/xerces.jar to a temporary location (such as c:\temp), load the efix
   and move the file back to it's original location.



Additional Information:
------------------------------------------------------------------