IBM Support

IT36491: RDQM creation might fail due to port conflict

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

  • The problem started when a new queue manager was created  with
    DR port 7094.
    Internally RDQM uses ports between 7000 to 7100 for its HA drbd
    replication connections. Coincidentally the port picked for the
    HA connection was also 7094 and hence this caused a conflict in
    the configuration.
    The following errors may be observed:
    Creating replicated data queue manager configuration fails with.
    AMQ3817E: Replicated data subsystem call '/usr/sbin/drbdadm --
    create-md qm1' failed with return code '10'.
    /etc/drbd.d/qm1.res:0: in resource qm1
    ipv4:123.456.789.111:7094 is also used
    /etc/drbd.d/qm1.dr.res:31 (resource qm1.dr)
    AMQ3812E: Failed to create replicated data queue manager
    The drbdadm-status output for the node shows the following
        # No currently configured DRBD found.

Local fix

Problem summary

  • ****************************************************************
    All IBM MQ users using RDQM feature.
    Platforms affected:
    Linux on x86-64
    During the creation of an RDQM queue manager, MQ picked a port
    for the DRBD connection which was already in use by the queue
    manager for the DR connection.  The queue manager failed to
    check whether the port was already in use.

Problem conclusion

  • The code has been modified to validate the port number before
    assigning it for use by a new RDQM for its DRBD connection.
    The fix is targeted for delivery in the following PTFs:
    Version    Maintenance Level
    v9.2 LTS
    v9.x CD    9.2.3
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'

Temporary fix


APAR Information

  • APAR number


  • Reported component name

    MQ BASE V9.2

  • Reported component ID


  • Reported release


  • Status


  • PE




  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date


  • Closed date


  • Last modified date


  • 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 BASE V9.2

  • Fixed component ID


Applicable component levels

[{"Type":"MASTER","Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
02 July 2021