PQ52124: DURING BBOASRX(CR) TERMINATION, CEEDUMP WAS PRODUCED FOR SIGSEGVBOSS_ADDRESS_SPACE::WRITE_BASCB_FIELD(FIELDS,VOID*)

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
During BBOASRx(CR) termination, CEEDUMP was produced for SIGSEGV
in BOSS_Address_Space::write_bascb_field(fields,void*).
It seems to be bbo3bas failed to access to BACB.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0 for z/OS and OS/390.                    *
****************************************************************
* PROBLEM DESCRIPTION: SIGSEGV for ABEND0C4/ABENDS0C4 in       *
*                      RasLock::releaselocknocheck in          *
*                      bborlock.cpp after ABEND0D6/ABENDS0D6   *
*                      from BBO3SETS called from               *
*                      BOSS_Address_Space::write_bascb_field   *
*                      during server region termination.       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During server region termination, after freeing the trace
object, the server may take an 0D6 abend trying to clear the
pointer to the BTRC because the CTL region PC routine required
to clear the pointer is gone because the CTL region terminated
prior to the server region.  The first processing the signal
handler for the 0D6 is to attempt to unlock the mutex which
protects the trace processing.  However, this object has
been freed (and the pointer not cleared, as above).  The
attempt to release the mutex results in an ABEND0C4.  This
results in another signal for which the signal handler
fails the same way, in a loop until something stops it (not
clear what that was).
Problem conclusion
Support was added to bborexit.cpp to conditionally proceed with
the trace unlocking process during signal handler execution
based on whether trace objects can be found.

APAR PQ52124 is associated with SERVICE LEVEL W400035 of
WebSphere Application Server V4.0 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ52124
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-09-06
Closed date 2001-09-17
Last modified date 2001-10-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOREXIT BBOUBINF        

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R400 PSY UQ57706    UP01/09/26 P F109

  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


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ52124
IBM Group: Software Group
Modified date: Oct 3, 2001