Fix (APAR):  PK11286

Status:  Fix

Release:  5.1.1

Operating System:  All

Supersedes Fixes:  Pre-requisite Fixes:

CMVC Defect:  PK11286

Byte size of APAR:  12164

Date: 2005-09-02

Abstract:  Server fails to start due to corrupt tranlog file

Description/symptom of problem:  
Unable to restart WebSphere Application Server. The following
messages appeared on the administrative console:
ADMU0116I: Tool information is being logged in file
D:\WebSphere\AppServer\logs\server1\startServer.log
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3011E: Server launched but failed initialization. Server
log files should contain failure information.
Additionally, the following error messages were recorded
in the SystemOut.log file:
8/22/05 10:24:05:023 EDT] 7d25eb84 RecoveryManag W WTRN0019E:
The transaction service log file tranlog has become corrupted.
[8/22/05 10:24:06:070 EDT] 7d25eb84 RecoveryManag E WTRN0025E:
Recovery of Transaction failed java.io.IOException: tranlog
corrupted
This problem is caused by the recovery log service recreating an
invalid transaction service 'state' record upon server restart. This only
occurs when there is an indoubt transaction record in the tranlog
file at the time the server shuts down. Classes DataItem, SingleDataItem
and RecoverableUnitSectionImpl will be updated to ensure that
the transaction service 'state' record is recreated correctly.
The fix for this APAR is currently targeted for inclusion in
fixpack 5.1.1.7. Please refer to the Recommended Updates page
for delivery information:
http://www-1.ibm.com/support/docview.wss?rs=180
&context=SSEQTP&uid=swg27004980



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: