PM41912: LOGGING OF THREAD POOL BUFFER EXPANSION CAN CAUSE STACK OVERFLOW ERRORS

8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
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

• An issue exists in which logging of a thread pool's request
  buffer expansion can lead to a loop in rare cases, ultimately
  resulting in a stack overflow.  This APAR avoids that condition.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: StackOverflowError can result from      *
  *                      logging that a thread pool is maxed.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If a thread pool has reached capacity and more requests on
  that pool are made, the thread pool will log a message with
  key of WSVR0630I.  The logging framework may attempt to
  forward that message using a new thread - which could be
  attempting to use the same thread pool that just reached
  capacity, leading to further log messages requiring more
  logging threads.  This will eventually lead to a
  StackOverflowException.
  

Problem conclusion

• This problem is resolved by changing the thread pool logic
  that logs this message.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.1.  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