PH61541: WEBSPHERE APPLICATION SERVER TRADITIONAL V9 CONTROL REGION A 0C4 ABEND +16A6 INTO BBOOWORK

APAR status

• Closed as program error.

Error description

• Control region log presented:
  BBOO0045E Internal failure, REASON=C9C20040.
  
  then captured a dump and abended with:
  ABEND=SDC3 U0000 REASON=000C000B
  
  The Servant regions experienced many timeouts which were
  reflected in the CR log as BBOO0327I HTTP REQUEST TIMEOUTs
  before abending as well. The timestamps indicated no delays in
  queuing, dispatching, or handing the response to the CR.
  
  IP ST showed an 0C4 at PSW 1A5184EE.
  IP SUMM FORMAT showed it on TCB 009A8BE0
  There's a linkage stack entry.
  Looking at storage at the PSW it looks like we're about +16A6
  into BBOOWORK.
  Traceback:
  bbgboa::bbo3stmr__FP4bacbUiPPUiPUi+0xd10"  in yours is confusing
  
  Traceback:
  
  DSA   Entry    E Offset Statement  Load Mod       Program
  
  
  1    bbooswrk(BBOOSWRK_Functions,acrt*,acrw**)
  
             -00214260       *PATHNAM
  
  2    BBO_BOA::getHiPriorityWorkElement(acrt*)
  
             +0000004C       *PATHNAM
  
  3    ACR_ExecutionThread::getAcrwToProcess()
  
             +00000148       *PATHNAM
  
  4    ACR_ExecutionThread::RemoveAndProcessWork(ThreadCleanUp*)
  
  
             +00000336       *PATHNAM
  
  5    CR_HiPriorityWorkRoutine
  
             +000001CA       *PATHNAM
  
  6    CELQPCMM  +00000F68       CELQLIB       CELQPCMM
  
  It appears WAS tried to load off of the address in R4 while
  executing in BBOOWORK, but something zeroed out R4, removing the
  valid address the code had loaded there earlier.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  V9.0                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: WEBSPHERE APPLICATION SERVER            *
  *                      TRADITIONAL                             *
  *                      V9 CONTROL REGION A 0C4 ABEND +16A6     *
  *                      INTO                                    *
  *                      BBOOWORK                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  ABEND0C4/ABENDS0C4 in controller +16A6 into bboowork because the
  upper part of an address has been zeroed.
  Control region log presented:
  BBOO0045E Internal failure, REASON=C9C20040.
  then captured a dump and abended with:
  ABEND=SDC3 U0000 REASON=000C000B
  The Servant regions experienced many timeouts which were
  reflected in the CR log as BBOO0327I HTTP REQUEST TIMEOUTs
  before abending as well. The timestamps indicated no delays in
  queuing, dispatching, or handing the response to the CR.
  Traceback:
  DSA   Entry    E Offset Statement  Load Mod       Program
  1    bbooswrk(BBOOSWRK_Functions,acrt*,acrw**)
  -00214260       *PATHNAM
  2    BBO_BOA::getHiPriorityWorkElement(acrt*)
  +0000004C       *PATHNAM
  3    ACR_ExecutionThread::getAcrwToProcess()
  +00000148       *PATHNAM
  4    ACR_ExecutionThread::RemoveAndProcessWork(ThreadCleanUp*)
  +00000336       *PATHNAM
  5    CR_HiPriorityWorkRoutine
  +000001CA       *PATHNAM
  6    CELQPCMM  +00000F68       CELQLIB       CELQPCMM
  

Problem conclusion

• When the head pointer to the ACRW queue is retrieved, there is
  a
  small timing window where another thread could potentially get
  an
  ACRW off the queue and begin clearing it out. When the original
  thread attempts to read the next pointer, it reads a bad value
  (leading zero) and ABENDs.
  
  Code has been added to zero out the next and previous pointers
  when an ACRW is taken from the queue, before the storage area
  is
  cleared.
  
  The fix for this APAR is targeted for inclusion in fix pack
  9.0.5.21 and 8.5.5.27. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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 FOR Z

• Fixed component ID

  5655I3500

Applicable component levels