Fix (APAR): PK50967 Status: Fix Release: 6.0.2.23,6.0.2.21 Operating System: Windows Supersedes Fixes: CMVC Defect: PK50967 Byte size of APAR: 37573 Date: 2008-02-01 Abstract: Application Server prints a verbose warning when it fails to rollover a log file. Description/symptom of problem: PK50967 resolves the following problem: 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: none. 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: None 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_.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 Directions to apply fix: NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environment. * Be Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.5 or later of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateInstaller/version.txt The update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg24008401 For detailed instructions on how to extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27006162 1) Copy 6.0.2.21-WS-WAS-IFPK50967.pak file directly to the maintenance directory. 2) Shutdown Application Server. Manually execute setupCmdLine.bat in Windows or ../setupCmdLine.sh in UNIX from the Application Server instance that maintenance is being applied to. 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. 3) Launch the Update Installer. 4) Enter the installation location of the Application Server product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (6.0.2.21-WS-WAS-IFPK50967.pak file which was copied into the maintenance directory). 7) Install the maintenance package. 8) Restart Application Server. Fix applies to Editions: Release 6.0 _X Application Server (Express or BASE) _X Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes __ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy PKxxxxx.pak file directly to the maintenance directory 2) Shutdown IBM WebSphere Application Server Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the IBM WebSphere Application Server instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the IBM WebSphere Application Server product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) Restart IBM WebSphere Application Server Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environment. * 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 removed, and fix3 re-applied. 1) Shutdown Application Server. Manually execute setupCmdLine.bat in Windows or ../setupCmdLine.sh in UNIX from the WebSphere instance that uninstall is being run against. 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) Launch the Update Installer. 3) Enter the installation location of the IBM WebSphere Application Server product you want to remove the fix. 4) Select the "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (6.0.2.21-WS-WAS-IFPK50967.pak). 6) Uninstall the maintenance package. 7) Restart Application Server. 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 removed, and fix3 re-applied. 1) Shutdown Application Server Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the Application Server instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the Application Server product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak). 6) Uninstall maintenance package. 7) Restart the Application Server. Directions to re-apply fix: 1) Shutdown Application Server. 2) Follow the Fix instructions to apply the fix. 3) Restart Application Server. Additional Information: