PQ90683: When running low on storage, a loop can occur between TraceWrite and TraceRecord

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
An SVCDUMP was obtained due to an out of storage condition
within a WebSphere server controller region. One of the threads
appears to have an infinite loop in the LE Traceback: with
module TraceWrite calling TraceRecord which calls TraceWrite
again which calls TraceRecord again, over and over for thousands
of iterations.
  When the first out of storage condition was detected, the
route TraceRecord was called to put out an error message.
TraceRecord calls TraceWrite to get the error message displayed.
TraceWrite attempts to get some storage for a buffer, but
because there is no storage available it attempts to issue
another storage shortage message. It calls TraceRecord for this
purpose. The problem is that if storage is not available to
issue a message, we should not attempt to issue a message, since
that attempt will also most likely fail.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: An infinite loop occurs with TraceWrite *
*                      calling TraceRecord calling TraceWrite  *
*                      when a trace record is written and      *
*                      storage is not available for            *
*                      TraceWrite.                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When an out of storage condition occurs while attempting to
write a trace record, we incorrectly attempt to write a trace
record to record the out of storage condition.  This results
in an infinite loop with TraceWrite calling TraceRecord which in
turn calls TraceWrite again over and over.
Problem conclusion
Code modified to stop writing a trace record in an out of
storage condition in TraceWrite.

APAR PQ90683 is associated with SERVICE LEVEL W502013 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ90683
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-06-26
Closed date 2004-07-20
Last modified date 2004-08-04

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
PQ90685

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ90831    UP04/07/27 P F407

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ90683.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ90683
IBM Group: Software Group
Modified date: Aug 4, 2004