PI16910: PLUGIN LOG SIZES CAN NOT BE CONTROLLED

8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as new function.

Error description

• Add ability to use IBM HTTP Server function to rotate plugin
  logs.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server plugin     *
  *                  users using Apache or IBM HTTP Server       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Plugin logfile can grow very large      *
  *                      quickly and there is no way to          *
  *                      control the size.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The plugin log file can grow very large especially when
  running in trace or debug mode. There is currently no way to
  manage this log file.
  

Problem conclusion

• If using an apache based webserver (such as IBM HTTP Server),
  you can take advantage of a webserver based function (piped
  logging) to manage the logfile. Information about apache piped
  logging function can be found at
  http://httpd.apache.org/docs/2.2/programs/rotatelogs.html
  
  Enter the piped log string desired in the plugin's "log file
  name" field within the Admin Console prior to
  generating the plugin configuration to use this function.
  Example:
  |bin/rotatelogs.exe c:/plugin-test/http_plugin.log 600
  This would cause the plugin log file to be rotated every
  600 seconds. The plugin module is invoked upon request
  processing so if there are no requests, the log will not be
  rotated until a request is received.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.3.  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP