IBM Support

PI79561: ADD A TIMER TO ABEND SERVANT AT SHUTDOWN IF THERE ARE STALLED THREADS

Fixes are available

8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using a setup like this:
    BBOM0001I protocol_https_timeout_output_recovery: NOT SET,
    DEFAULT=SERVANT.
    BBOM0001I server_region_stalled_thread_threshold_percent: 25.
    
    And a thread times out, but the servant isn't abended (due to
    server_region_stalled_thread_threshold_percent not being
    reached) and is still running when the sever is shut down, this
    can cause the servant to not shut down.  A property needs to be
    added to set a timer that will abend the servant is there are
    stalled threads that have timed out that are still running when
    the server is shut down.
    

Local fix

  • cancel the server if it doesn't shut down
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5 and V9.0 for z/OS               *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server for        *
    *                      z/OS controller does not stop when      *
    *                      requested.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using server_region_stalled_thread_threshold_percent a
    server does not stop when requested because there are still
    hung threads in a servant. A server will not stop until
    all servants come down.
    

Problem conclusion

  • Updated the stop code to abend servants with hung threads when
    control_region_on_stop_abterm_hung_sr_waittime is set
    to a value greater than 0.
    When control_region_on_stop_abterm_hung_sr_waittime is set to
    the default of 0 servants with hung threads will not be abended.
    When control_region_on_stop_abterm_hung_sr_waittime is set to
    a value other than 0, the controller will wait that many
    seconds before looking to see if there are servants with
    hung threads that need to be abended. The abend code used will
    be EC3 with reason code 042B0001.
    
    APAR PI79561 is currently targeted for inclusion in Fix Packs
    8.5.5.12 and 9.0.0.5 of WebSphere Application Server.
    
    Please refer to the Recommended Updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    
    In addition, please refer to URL:
    http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack PTF information.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI79561

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-06

  • Closed date

    2017-04-26

  • Last modified date

    2017-04-26

  • 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

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
06 December 2021