IBM Support

IT44268: Following an HA reconnection, the queue manager no longer runs on the preferred node

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

  • After a high availability (HA) queue manager reconnection event
    on the IBM MQ Appliance, the queue manager is intermittently
    observed running on a partner node instead of the specified
    preferred node.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    MQ Appliance users on version IBM MQ 9.3 who are using a high
    availability queue manager.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When an HA reconnection event takes place, it is expected that
    the queue manager will run on the preferred node.
    However, it was found that, intermittently, the queue manager
    was running on the partner nodes instead.
    
    This was due to a defect in the code which failed to refresh the
    transient attributes for the preferred node during reconnection
    of the primary, secondary, and replication interfaces.
    
    This resulted in the queue manager running on a partner node
    instead of the primary, which is the queue manager's preferred
    location, after the reconnection of the network.
    

Problem conclusion

  • The code change associated with this APAR updates the MQ
    Appliance behaviour to check if transient attributes have been
    previously set before setting it itself, so these do not get
    lost after a synchronisation operation.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.3 LTS   9.3.0.10
    v9.x CD    9.3.3
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT44268

  • Reported component name

    MQ APPLIANCE M2

  • Reported component ID

    5900ALJ00

  • Reported release

    930

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-08-01

  • Closed date

    2023-08-24

  • Last modified date

    2023-10-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

    MQ APPLIANCE M2

  • Fixed component ID

    5900ALJ00

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.3","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
16 October 2023