eFix (APAR): PQ62277

Status:      E-Fix

For Release: WebSphere 3.5.4, 3.5.5, 3.5.6, 4.0.1, 4.0.2 & 4.0.3

For Edition: WebSphere AE

For ContainerTypes: All

For Operating System:

Supersedes eFixes: PQ52182

Pre-requisite eFixes: None

Date: 27/06/02

Abstract: Data corruption in distributed websphere tranasction following a rollback in one server
          in Interoperability mode.


Description/symptom of problem:
        When completing a distributed transaction on two servers, the
        coordinating server asks the subordinate server to prepare to
        commit. If the subordinate server elects to rollback and rolls
        back, this decision is not passed back to the coordinating
        server, which commits its portion of the transaction,
        resulting in inconsistent data. No error messages or exceptions
        are generated. If the subordinate server elects to commit,
        the coordinating server also commits as expected. This problem
        has only been observed when WebSphere is configured to run in
        Interoperability mode.

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 <jarfile name>

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/<APAR#> 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/<APAR#>).

2) Shutdown WebSphere

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

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