IBM Support

PM29466: INTERMITTENT SOC4 IN 64-BIT WEBSPHERE FOR Z/OS CONTROL REGION

Fixes are available

6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • WebSphere for z/OS servers running 64-bit may encounter
    intermittent S0C4 ABENDs in the Control Region when processing
    an IIOP request. The corresponding SVCDUMP may show the
    following stack trace and corrupted DSA chain:
    --
    DSA Entry E Offset Statement Load Mod  Program Unit    Service
    Status
    
    1   bbooeqgq(ENQ_DEQ_RName*,SEQUENCE_octet*,int,int,int,int*,int
                    +00000708              *PATHNAM          CF13103
    Call
    2   BBO_BOA::checkTransactionAffinity(ORB_Request*,AffinityRestr
                    +000006E0              *PATHNAM          CF13103
    Call
    WARNING  An invalid DSA pointer was found on traceback while
    processing DSA: 0000000A_85CF5F60 and CAA: 0000000A_85EFECF0
    
    DSA DSA Addr E Addr PU Addr PU Offset Comp Date Compile Attribut
    1        0000000A_85CF4520  00000000_7CA0EB50  00000000_00000000
    +7CA0F2580  20101001   C/C++     POSIX XPLINK EBCDIC  IEEE
    2        0000000A_85CF4920  00000000_7C859C78  00000000_00000000
    +7C85A3580  20101001   C/C++     POSIX XPLINK EBCDIC  IEEE
    
    WARNING  An invalid DSA pointer was found on traceback while
    processing DSA: 0000000A_85CF5F60 and CAA: 0000000A_85EFECF0
    --
    
    Often the server terminates happens due to a S0C4 on a
    different TCB a few seconds later. For example:
    --
    TCB 8cb598
    Dsa         Entry      Offset     Function
    ---         -----      ------     --------
    9bfcf7f20   1ad36d80   000077e8   CELQDMDR
    9bfcf99c0   1ad4e678   00001364   CEEKDUMP
    9bfcfa2e0   1ae1b0c8   000047d4   CEEHDSP
    9bfcfcc00   1b01b620   000013e2   CEEOSIGG
    9bfcfda20   1ae2f3c8   00000392   CEEHSGL
    9bfcfdcc0   1ae2fec0   00000068   CEEHSGLT
    9bfcfdee0   1aecfb18   00001946   CEEOPCB
    9bfcfe260   1b17f000   0000003e   pthread_cond_broadcast
    9bfcfe360   1d43de28   000001b2   j9thread_monitor_notify
    9bfcfe460   1d390700   00c54728   RUNJAVATHREAD
    9bfcfe8a0   1d409580   000000e0   javaProtectedThreadProc
    9bfcfe9a0   1d4ad268   0000071a   j9sig_protect
    9bfcff1a0   1d40c0b8   00000072   javaThreadProc
    9bfcff2a0   1d43b5e0   0000051c   thread_wrapper
    9bfcff3a0   1aed60d8   00000f56   CELQPCMM
    --
    
    However Logrec should show the first S0C4 to be from function
    bbooeqgq(ENQ_DEQ_RName*,SEQUENCE_octet*,int,int,int,int*,int
    

Local fix

  • Run servers in 31-bit to avoid this problem
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V6.1.0                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABEND0C4/ABENDS0C4 in WebSphere for     *
    *                      z/OS controller in glue routine         *
    *                      bbgqeqgq.cpp.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The glue routine is invoked within the 64-bit controller
    to invoke the 31-bit routine bbooeqgq.plx to determine, based
    on transaction affinity, if an inbound IIOP request should
    receive a forwarding IOR or be processed by the current server.
    
    An uninitialized parameter, representing a forwarding IOR
    length, resulted in the glue routine moving a very large amount
    of storage from the 31 bit heap area to the caller supplied
    output IOR area; within the C++ call stack storage.  This
    corrupted the call stack storage as well as resulted in an
    ABEND 0C4 within the glue routine.
    

Problem conclusion

  • Code has been modified within the bbgqeqgq.cpp glue routine to
    initialize the IOR length parameter prior to the call to the
    31-bit bbooeqgq.plx routine.  Routine bbooeqgq only sets the
    IOR length parameter if intending to pass back a forwarding IOR
    to the caller.
    
    APAR PM29466 is currently targeted for inclusion in Service
    Level (Fix Pack) 6.1.0.37 of WebSphere Application Server V6.1.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM29466

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-23

  • Closed date

    2011-01-07

  • Last modified date

    2011-05-02

  • APAR is sysrouted FROM one or more of the following:

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

    PM29467

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R610 PSY UK65883

       UP11/04/06 P F104

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

More support for: WebSphere Application Server for z/OS
General

Software version: 6.1

Reference #: PM29466

Modified date: 02 May 2011