IBM Support

PI37801: THREAD SLEEP IN WLM RULE.ETIQUETTE REGISTERNOTIFICATIONTYPE CAUSES THREAD HANGS WHEN CLUSTER MEMBER DESCRIPTIONS NOT AVAIL

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A Thread sleep in WLM RuleEtiquette.registerNotificationType
    was causing thread hangs when cluster member descriptions were
    not available. Code was changed to skip the wait loop to avoid
    thread hangs while descriptions are propagating.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0, V8.0, and V8.5 workload        *
    *                  management (WLM)                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Thread hangs can occur with             *
    *                      RuleEtiquette.registerNotificationType  *
    *                      on stack                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The WLM rule processing code was waiting asynchronously for
    descriptions of members as they are started. Descriptions are
    received for these members on the IIOP request response flow.
    If the description for a newly started member is not included
    in an IIOP response to the client, the thread will sleep in an
    attempt to wait for the necessary description. However there
    is no other mechanism from which a description can be expected
    in this request flow so waiting is of no value and can lead to
    a hung thread.
    

Problem conclusion

  • A custom property IBM_CLUSTER_HANDLE_DESCRIPTION_WAIT is added
    to skip thread sleep processing if no description is received
    for the RuleEtiquette to act on. The description will be
    processed later as it is included in a future IIOP response.
    
    To define the IBM_CLUSTER_HANDLE_DESCRIPTION_WAIT custom
    property for the cell:
    
    1. In the administrative console, select System administration
    > Cell > Custom properties > New.
    2. Set the property name to IBM_CLUSTER_HANDLE_DESCRIPTION_WAIT
    and value to false.
    3. Click OK, and save your changes.
    
    The change takes effect the next time that a server is
    started.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.41, 8.0.0.12, and 8.5.5.6.  Please refer to the
    Recommended Updates page for delivery information:
    
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI37801

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-03-25

  • Closed date

    2015-06-05

  • Last modified date

    2016-11-29

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PI37801

Modified date: 29 November 2016