Fixes are available
PK50967; 6.0.2.21/6.0.2.23: TRAS0016E: Exeption while trying to archive log file
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
TRAS0016E: An unexpected exception while trying to archive log file when IBM WebSphere Application Server is running under Test environment of Rational Application Developer. The log files are supposed to be locked by other processes like RAD, RSA and Eclipse which results in the application server not able to rename the file which is scheduled for file rotation when the file size reaches to the value specified in "logs and traces" option of Application Server administrative console. This APAR will attempt to copy the log file over if the rename fails during the rollover process.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users who run IBM WebSphere Application * * Server versions 6.0.2 and 6.1 in a * * development environment such as Eclipse, * * Rational Application Developer, and so on * * or any user who monitors WebSphere * * Applicaiton Server log files in a "file * * locking" text editor. * **************************************************************** * PROBLEM DESCRIPTION: Application Server prints a verbose * * warning when it fails to rollover a * * log file. * **************************************************************** * RECOMMENDATION: * **************************************************************** Application Server attempts to roll over a log file by stopping all output, then renaming the existing file (that is, from SystemOut.log to SystemOut_<timestamp>.log), then resuming output to a new file called SystemOut.log. If the rename operation fails (usually because another process like WordPad, Eclipse or other has locked the log file), Application Server will write a verbose error message with the message ID, TRAS0016E, and will continue logging to the same file.
Problem conclusion
While it is impossible for Application Server to force the rename when the operating system fails to rename the file, Application Server can attempt the rollover by copying the existing log file to a new file with the timestamp appended, and then write-over the original log file. This makes it possible to roll over log files even when the rename operation fails. Application Server will still write a warning message when the rename fails. This is because a copy operation is significantly slower than a rename operation, so system performance can be affected. Also, it is possible that the copy operation will fail (due to insufficient disk space, or some other error). In this case, Application Server will log a verbose error message, so that the root cause of the copy failure can be identified. The fix for this APAR is currently targeted for inclusion in fixpacks 6.0.2.25 and 6.1.0.15. 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
PK50967
Reported component name
WEBSPH APP SERV
Reported component ID
5724J0800
Reported release
60W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-08-14
Closed date
2007-10-04
Last modified date
2008-02-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
RAS
Fix information
Fixed component name
WEBSPH APP SERV
Fixed component ID
5724J0800
Applicable component levels
R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
Document Information
Modified date:
29 December 2021