IBM Support

IT33929: If an rdqmadm process is interrupted before completion then subsequent rdqmadm commands fail with AMQ3793E

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 the 'rdqmadm -p' command is issued on a secondary RDQM node
    to make it the primary node in the cluster, it attempts to
    acquire an internal lock which fails.
    The command fails with
    AMQ3793E and AMQ3870E written to the CLI:
    AMQ3793E: The replicated data subsystem was unable to take the
    control command lock after 30 seconds.
    AMQ3870E: Failed to set preferred replicated data node for
    queue manager 'RDQM1'.
    
    This is caused by a previous instance of the rdqmadm process
    which was ended abruptly by a SIGINT (ctrl+c) and left behind
    orphaned locks on the node where the command was ran.
    

Local fix

  • Reboot the node which is unable to become primary. This will
    clear out any orphaned locks and will allow the node to become
    the primary RDQM node when the command is run again.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All IBM MQ users who use Replication Data Queue Manager (RDQM)
    feature.
    
    
    Platforms affected:
    Linux on x86-64
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The lock held by the command process is not released when the
    command is abruptly terminated. A logic omission for this
    scenario in the RDQM lock validation routines meant that the
    subsequent commands failed while trying to acquire the orphaned
    lock.
    

Problem conclusion

  • The code is modified to detect and release the orphaned lock.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.8
    v9.x CD    9.2.2
    
    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

    IT33929

  • 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

    2020-08-17

  • Closed date

    2021-01-22

  • Last modified date

    2021-01-22

  • 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

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

Document Information

Modified date:
23 January 2021