IBM Support

PH35522: WEBSPHERE APPLICATION SERVER SERVANT OR ADJUNCT REGION MAY NOT COME DOWN QUICKLY AFTER A 5C6 ABEND

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The WebSphere Servant or Adjunct Region does not come down
    quickly after a 5C6 abend if there are threads waiting for work
    from WLM that can not be interrupted by a signal.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V9.0 for z/OS                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: The WebSphere servant or adjunct        *
    *                      region does not come down quickly       *
    *                      after a ABEND5C6/ABENDS5C6 if there     *
    *                      are threads waiting for work from WLM.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The WebSphere servant or adjunct region does not come down
    quickly after a 5C6 abend or a call to exit if there are
    threads waiting for work from WLM. The threads that are waiting
    for work from WLM can not be interrupted by a signal until
    they return from WLM. The servant region does not come down
    until enough work requests come in to release all the threads
    waiting for work from WLM.
    

Problem conclusion

  • The code was updated to abend the servant region main with
    ABENDEC3/ABENDSEC3 reason code 04020019 when the atexit
    routine detects that threads are still active.
    
    A new custom property
    servant_region_suppress_hung_thread_abend has been added.
    The default is 0 which causes the servant region main
    to be abended when active threads are detected by the
    atexit routine. If you set this property to 1, the atexit
    routine does not abend the servant region main.
    
    To set servant_region_suppress_hung_thread_abend using the
    admin console you can use
    Servers > Server Types > WebSphere application servers >
    select the server > Server Infrastructure > Administration >
    Custom properties > new
    or
    Environment > WebSphere variables > select scope > New
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.20 and 9.0.5.8. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH35522

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-03-18

  • Closed date

    2021-04-27

  • Last modified date

    2021-04-27

  • 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

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900"}]

Document Information

Modified date:
28 April 2021