IBM Support

IT29032: Replicated Data Queue Manager fails to start on any of the nodes.

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

  • In IBM MQ 9.1, Replicated Data Queue  Manager may end up in
    banned state on all 3 nodes and would not start on any of the
    nodes. The root-RDQM.LOG will record lines like the below
    indicating that the queue manager is in ban state on each of the
    nodes.
    
    location cli-ban-RDQM1-on-NODE001 qm1 role=Started -inf: NODE001
    location cli-ban-RDQM1-on-NODE002 qm1 role=Started -inf: NODE002
    location cli-ban-RDQM1-on-NODE003 qm1 role=Started -inf: NODE003
    
    RDQM1 is the queue manager name and NODE00* are the node name
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using Replicated Data Queue Managers (RDQM).
    
    
    Platforms affected:
    Linux on x86-64
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Certain sequence of network failures will force the replicated
    data queue manager (RDQM) into a 'banned' state on all three
    nodes.  Though this is expected to be cleared internally it was
    not happening in certain cases.  As a result the RDQM could not
    be started on any of its nodes.
    

Problem conclusion

  • The RDQM code has been modified such that the banned state can
    be handled programmatically.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 CD    9.1.3
    v9.1 LTS   9.1.0.4
    
    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

    IT29032

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-05-06

  • Closed date

    2019-10-01

  • Last modified date

    2019-10-14

  • 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

    IBM MQ BASE MP

  • Fixed component ID

    5724H7271

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
14 October 2019