Fixes are available
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
Product Version: Base edition, V8.0.0.2 OS: Linux, Java Version:1.6.0 Problem Description: TextLog.log getting created with same timestamp which result in over writing of trace There was a spike of log records from 12:15:18:000 to 12:15:18:849 which filled up the whole 5Mb of a TextLog_12.04.05_12.51.18.log. The next log file was named TextLog_12.04.05_12.51.18.log as well due to the first record timestamp having the same value in seconds. That resulted in previous file with all its record to be overiden. The workaround is to use HPEL binary repository which uses milliseconds in its file names instead of TextLog_* files. Use logViewer.sh to generate the same info as recorded in TextLog_* files.
Local fix
The workaround is to use HPEL binary repository which uses milliseconds in its file names instead of TextLog_* files. Use logViewer.sh to generate the same info as recorded in TextLog_* files.
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM WebSphere Application Server * * V8.0 switched to HPEL mode with TextLog * * enabled. * **************************************************************** * PROBLEM DESCRIPTION: Log data can be lost if more than 5Mb * * of records are emmitted in 1 second. * **************************************************************** * RECOMMENDATION: * **************************************************************** Names of TextLog files contain timestamps with precision up to a second. If the amount of log records generated require creation of a new file in under one second the name of the new file is the same as previous file and that results in over writing of the previous TextLog file.
Problem conclusion
The fix ensures that new TextLog file is not started until its name is different than TextLog file currently in use. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.4. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM62402
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-04-12
Closed date
2012-04-27
Last modified date
2012-04-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R800 PSY
UP
Document Information
Modified date:
28 October 2021