PM47974: REDUCE THE SPEED OF LOGGING TO ALLOW THE LOGGER THREAD TO KEEP U P WITH LOGGING

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

• The server can get into an OutOfMemory sitation when a sustained
  amount of logging is happening at high volumes
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Version    *
  *                  v8.0 users of National Center for           *
  *                  Supercomputing Applications (NCSA) Access   *
  *                  logging or proxy access logging             *
  ****************************************************************
  * PROBLEM DESCRIPTION: The logging queue can become large      *
  *                      and possibly cause memory issues        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When there is a state of sustained high volume, logging
  entries can cause memory issues. This can possibly cause
  memory issues(such as out of memory) because the logging code
  can not write the data out fast enough and more entries
  continue to go onto the queue
  

Problem conclusion

• Added the HTTP Channel custom property
  "SustainedHighVolumeLogging"(true/false(default)) to allow the
  logging code to attempt to catch up with the backlog of
  entries. The new custom property is set on this panel in the
  Administrative Console:
  Application Servers > {Server Name} > Web Container Transport
  Chains > {Chain Name} > {HTTP Channel Name} > Custom Properties
  
  This functionality was also added for the proxy logging. The
  new property is
  "http.sustained.high.volume.logging"(true/false(default)).
  This can be set as a custom property on this panel:
  WebSphere proxy servers > {Proxy Server name} > HTTP Proxy
  Server Settings > Proxy settings > Custom properties
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.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

• R800 PSY

     UP