IBM Support

PM86657: MDB TIMEOUT LED TO THE SR TERMINATION WITH AN ABEND EC3 04130008 DUE TO A MISCALCULATION OF THE CR DISPATCH TIMER FOR MDB REQUEST

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The Hung Thread Recovery code successfully nudged the servant
    the MDB Plan "A" request to complete.  We observed the BBOJ0113I
    and associated  traces within the servant.  However, at the same
    time a dispatch timer  in the controller expired.  It begin the
    cleanup for the MDB Plan "A"  request   with an ORB_Request Id
    of x'FFFFFD3C' at the same time.   The controller processing of
    the dispatch timer generates an error response for the request
    and then cleans up the MDB Request from the server.  Part of the
    cleanup is to forceable terminate the servant if the request is
    still under dispatch; in this scenario it was as seen in the
    dump.  The problem is that the timer in the controller expired
    too soon to allow the Hung Thread Recovery code in the servant
    to break the dispatched request out of its hang and end on its
    own, and thus avoid the ABTERM of the servant.   This is an
    error in the calculation of the controller dispatch timer for
    MDB Plan "A".  If the control_region_mdb_request_timeout is set
    to value under 1 hour (roughly 3596 seconds) the controller does
    NOT add additional time to the dispatch alarm to allow the Hung
    Thread Recovery function in the servant time to interrupt the
    dispatched request.
    This problem occurs only on Websphere z/OS v7.0.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
    *                      servant process ABEND0EC3,              *
    *                      REASON=04130008 for MDB Plan "A"        *
    *                      request.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A MDB Request from Plan "A" (Listening in the Controller.  A
    variant of "ASF message-driven beans with WebSphere MQ as the
    messaging provider) timed out in the Servant.  The Hung Thread
    Recovery function had driven an ODI to attempt to shake the
    request out of a "hang"; message BBOJ0113I was observed in the
    target Servant for the MDB Request.
    The MDB Request should have been allowed to terminate and
    cleanup leaving the Servant up and running.  However, the
    Servant was ABTERM'd with an ABEND0EC3, RSN=04130008 at this
    time.
    The reason the Controller terminated the Servant was that its
    "fallback" Request timer expired.  The value used to set this
    timer did not allow time for the Hung Thread Recovery code to
    attempt to shake the request out of a "hang" situation.
    

Problem conclusion

  • Code has been modified in the MDB Plan "A" path to add in the
    same "fallback" time allowance that is added in all the other
    dispatch paths.
    
    APAR PM86657 is currently targeted for inclusion in Fix Pack
    7.0.0.31 of WebSphere Application Server.
    
    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

    PM86657

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-09

  • Closed date

    2013-04-17

  • Last modified date

    2014-02-05

  • 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

  • R700 PSY UI13725

       UP14/01/11 P F401

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: 7.0

Reference #: PM86657

Modified date: 05 February 2014