IBM Support

PH00566: Member should fail over after continuous 2 minutes sendHeartBeat failure.

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

  • When member keep failing to sendHeartBeat to Controller
    continuously for 2 minutes, it should fail over.
    
    A collective member's error handling for
    InstanceNotFoundException preserves the connection and
    allows it to continue heart beating on the assumption that
    it is a temporary situation, such as during controller start
    up. In the field we've seen a case where a controller began
    returning this exception for an extended period. We should
    handle this case on the member side by eventually failing
    the connection so the member can fail over to another
    controller.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty - Systems Management         *
    *                  Functions                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Collective member connection remains    *
    *                      open after failures to send heart       *
    *                      beats                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A problem at a collective controller may result in a member
    receiving InstanceNotFoundExceptions when attepting to send
    heart beats to that controller.  In a multicontroller collective
    this exception should cause the controller to fail over to a
    different controller.  Instead, the member continues attempting
    to send heart beats to the same controller.
    

Problem conclusion

  • When a member fails to send heart beats to a controller for 2
    minutes it will attempt a new connection.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 18.0.0.3.  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

    PH00566

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-07-16

  • Closed date

    2018-08-02

  • Last modified date

    2018-08-02

  • 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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels



Document information

More support for: WebSphere Application Server

Software version: CD0

Reference #: PH00566

Modified date: 02 August 2018


Translate this page: