PK64375; 6.0.2.27: Wrong file size value for diagnostic trace file

Download Description

PK64375 resolves the following problem:

ERROR DESCRIPTION:
The rollover size of a trace file can be set in the administrative console under Troubleshooting->Logs and Trace-> "server name" ->Diagnostic Trace->"Runtime" tab. When a user enters the rollover size into the "Maximum File Size" field, the value entered will be saved as the wrong value where the value gets multiplied by 1048576.

IBM® WebSphere® Application Server version 6.0.2.27.

Runtime diagnostic trace max file still broken after Interim Fixes.

1. Navigate to Logging and Tracing for any server, Diagnostic Trace Service -> Runtime.

2. Select File and change the Maximum File Size to "1" or any number. Click Apply and OK.

3. Go into Diagnostic Trace Service -> Runtime again. You will see that the number entered previously has been "converted" incorrectly to bytes (in this case "1048576"), even though the field is MB. Looking at the growth of the trace file, it seems that a value entered as 1MB and converted is really allowing a max of 1048576MB (or 1TB).

LOCAL FIX:
n/a

PROBLEM SUMMARY

USERS AFFECTED:
IBM WebSphere Application Server version 6.0.2 users configuring the trace or logging file size rollover.

PROBLEM DESCRIPTION:
Changing the rollover file size for the diagnostic trace file sets the wrong file size value.

RECOMMENDATION:
None

The rollover size of a trace file can be set in the administrative console under Troubleshooting->Logs and Trace->"server name" -> Diagnostic Trace->"Runtime" tab. When you enter the rollover size into the "Maximum File Size" field, the value entered will be saved as the wrong value, where the value gets multiplied by 1048576.

This problem is introduced by PK60511 and will be encountered in version 6.0.2.27 or if a previous Interim Fix for PK60511 has been applied. The current PK60511 Interim Fix that is available for download has been corrected.

PROBLEM CONCLUSION:
Code has been corrected to save the rollover size correctly.

6.0.2.25-WS-WAS-IFPK64375 can be applied to either WebSphere Application Server V6.0.2.25 or WebSphere Application Server V6.0.2.27. 6.0.2.25-WS-WAS-IFPK64375 should not be applied to V6.0.2.25 unless this problem is occurring after installing the Interim Fix for PK60511.

The fix for this APAR is currently targeted for inclusion in Fix Pack 6.0.2.29.

Please refer to the recommended updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980