IBM Support

PH58223: LOAD BALANCER NOT INVOKING CORRECT USER EXITS WHEN HIGH AVAILABILITY IS REMOVED

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 high availability is removed, the goInOp user exit should
    be invoked.
    
    The goInOp user exit is not invoked when high availability
    is deleted by the user. The goInOp user exit is invoked when
    the executor is stopped, but the goStandby user exit is
    invoked after goInOp.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Load Balancer users with      *
    *                  high availability and go scripts            *
    ****************************************************************
    * PROBLEM DESCRIPTION: With high availability and go           *
    *                      scripts, goStandby is invoked when      *
    *                      the executor is stopped. No scripts     *
    *                      run when HA is removed.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The Load Balancer allows users to write custom actions that
    occur with high availability state changes. These custom
    scripts are referred to as go scripts because of the required
    naming convention: goActive, goStandby, goInOp. The goActive
    script is invoked when high availability enters the active
    state; the goStandby script is invoked when high availability
    enters the standby state. The goInOp script is invoked when
    high availability is removed or stopped.
    The Load Balancer software is not calling goInOp when a user
    issues the "highavailability backup delete" command. When high
    availability is stopped because the executor is stopped, the
    goInOp script is invoked but shortly afterwards the goStandby
    script is invoked.
    

Problem conclusion

  • Corrected code not to call goStandby after goInOp when the
    executor is stopped; added invocation of goInOp when high
    availability is removed using the "highavailability backup
    delete" command.
    
    Fix levels:
       8.5.5.25
       9.0.5.19
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH58223

  • Reported component name

    WS EDGE LB IPV4

  • Reported component ID

    5724H8812

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-11-15

  • Closed date

    2023-11-16

  • Last modified date

    2023-11-16

  • 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

    WS EDGE LB IPV4

  • Fixed component ID

    5724H8812

Applicable component levels

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

Document Information

Modified date:
04 December 2023