PQ93139: com.ibm.ws.recoverylog.spi.InternalLogException causes application server not to start

 Fixes are available

PQ93139; 5.1.1: InternalLogException causes application server startup failure
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux



APAR status
Closed as program error.

Error description
com.ibm.ws.recoverylog.spi.InternalLogException during
application server startup causes it fail startup. The comes
from the JTA code trying to recover a log with a bad header.
Local fix
Remove tranlogs.
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users.      *
****************************************************************
* PROBLEM DESCRIPTION: During server startup an                *
*                      InternalLogException exception was      *
*                      received, and the server failed to      *
*                      start.                                  *
*                                                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
com.ibm.ws.recoverylog.spi.InternalLogException was reported
during application server startup which causes it to fail
to startup. The exception comes from the transaction service
which was performing recovery when it discovered a recovery
log file with a corrupted header. The specific corruption was
dicsovered in a recovery log file that was marked as being
keypointed. This particular error should not prevent server
recovery and startup.
Problem conclusion
Classes LogFileHeader, LogFileHandle and LogHandle have been
updated so that a corrupt header in a recovery log file
marked as keypointing does not prevent server recovery and
startup.
Temporary fix Comments
APAR information
APAR number PQ93139
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00I
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-08-20
Closed date 2004-10-05
Last modified date 2004-10-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
LOGFLEH LOGHDR LOGHNDL      

Publications Referenced

Fix information

Applicable component levels
R003 PSN    UP
R00A PSN    UP
R00H PSN    UP
R00I PSN    UP
R00P PSN    UP
R00S PSN    UP
R00W PSN    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00I
Software edition:
Reference #: PQ93139
IBM Group: Software Group
Modified date: Oct 5, 2004