Fix (APAR): PK72269 Status: Fix Release: 7.0 Operating System: AIX,HP-UX,i5/OS,IBM i,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,Solaris,Windows Supersedes Fixes: CMVC Defect: 538445 Byte size of APAR: 55205 Date: 2008-09-19 Abstract: Rollover of WebSphere Application Server log files are occurring a few bytes beyond the defined max size. Description/symptom of problem: PK72269 resolves the following problem: ERROR DESCRIPTION:? PK66795 is supposed to allow for rollover even if the log files had been truncated with an external tool. The calculation is incorrect causing the rollover to occur a few bytes over the defined max size. LOCAL FIX:? PROBLEM SUMMARY:? USERS AFFECTED: All users of WebSphere Application Server PROBLEM DESCRIPTION: Rollover of WebSphere Application Server log files are occurring a few bytes beyond the defined max size. RECOMMENDATION: None PK66795 is to allow for external tools to clear out the contents of WebSphere Application log files and still allow for the log file rotation to occur. This fix introduces a problem where the rotation occurs too late causing the historical file size to go over the defined max size. PROBLEM CONCLUSION:? Internal counters had been used to track file size for performance reasons. For the same performance reasons, PK66795 will only allow truncation of the log file. If an external tool appends to the log file, the rotation may continue to be thrown off. The fix to APAR PK72269 will prevent the log rotation to occur beyond the max size, with the same conditions mentioned for PK66795. PK66795 will not be supported for z/OS releases. The fix for this APAR is currently targeted for inclusion in fixpack 6.0.2.31, 6.1.0.21, 7.0.0.1. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Install Fix to all WebSphere installations unless special instructions are included below. Special Instructions: None NOTE: The user must: * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V7.0.0.0 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. This can be checked by reviewing the level of the Update Installer in file <UPDI_root>/updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24020212 1) The fix is delivered as a single file with a .pak extension (such as 7.0.0.1-WS-WAS-IFPK12345.pak). Copy the .pak file directly to the maintenance directory, <UPDI_root>/maintenance. 2) Shutdown WebSphere 3) For IBM i users, use the update command to install and uninstall the interim fix. The IBM Information Center can provide additional details, if needed, on the use of this command. http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=rins_update. For non-IBM i users, launch the Update Installer and click the Next button on the Welcome page. 4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button. 5) Select the "Install maintenance package" operation and click the Next button. 6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button. 7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step. The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed. Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package. To determine why some maintenance packages have been identified as not applicable, see description in log found in <UPDI_root>/logs/tmp*/updatelogs.txt 8) For all platforms except Windows. In pre-install summary panel, use the "verify permission" feature to verify the user has permissions to apply updates to files associated with the selected maintenance. Correct any file permissions before clicking next to start the install. 9) Restart WebSphere Directions to remove fix: 1) Shutdown WebSphere 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Select name of the maintenance package to uninstall (PKxxxxx.pak). Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * 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 WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere 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 WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: