PM48157: HPEL TEXTLOG IS CONFIGURED BEGIN CLEANUP OF OLDEST RECORDS BUT IT DIDN'T CLEANUP ANY OLDEST LOG FILES

8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
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

• High Performance Extensible Logging (HPEL) TextLog is
  configured to cleanup of oldest records using retention by
  size options but overall disk usage for TextLogs grows past
  configured value with new server restarts.
  
  Recreation steps
  
  In the console, under Troubleshooting->Logs and
  Trace->server1->configure HPEL Text log we have the following
  options set:
  
  Enable text log: checked
  Directory Path: c:\test
  Enable Log record buffering: checked
  Start new daily log file at: checked, 12am
  Begin cleanup of oldest records: checked, when log size
  approaches
  maximum
  Maximum log size: 10 megabytes
  Out of space action: purge old records
  Text output format: Basic
  Include trace records: checked
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: HPLE TextLogs size grows past           *
  *                      configured max with server restart.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  WebSphere Application Server was not correctly cleaning up
  HPEL TextLog files from previous server instances. The result
  was over time growth in the TextLog repositories max size
  beyond that which was configured.
  

Problem conclusion

• TextLog repository size will now work as expected. With this
  fix HPEL will now consider existing TextLog files in
  determining the size of the TextLog repository.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.2.  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 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