IBM Support

IT25741: MQ cluster full repository unable to complete "REFRESH CLUSTER" command, reporting AMQ9511 error

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • REFRESH CLUSTER fails on Full Repository queue manager on rare
    occasions.
    
    Additional symptoms include:
    --
    AMQ9511: Messages cannot be put to a queue.
    
    EXPLANATION:
    The attempt to put messages to queue
    'SYSTEM.CLUSTER.TRANSMIT.QUEUE' on queue
    manager 'xxxxxxx' failed with reason code 2041.
    
    The issue may also manifest as cluster resolution errors as a
    result of the failed refresh: "MQOPEN on object 'Q' returned
    2189
    Cluster resolution error."
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users running REFRESH CLUSTER on a Full Repository queue manager
    in a cluster.
    
    
    Platforms affected:
    Windows, Linux on zSeries, Linux on x86-64, Linux on x86, Linux
    on S390, Linux on Power, AIX, IBM iSeries
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    During REFRESH CLUSTER on a full repository, the MQ repository
    manager logic incorrectly attempted to send updates via cluster
    channels that were not marked as "in use".  Cluster channels not
    marked as "in use" can occur if, for example, the user
    introduces a queue manager with a channel name already in use in
    the cluster. This would replace the existing queue manager as
    the "in use" record. This configuration might have happened
    deliberately or by a user mistake and channels in this state
    will exist for a few weeks in the cluster even after the user
    deletes the QM that contains them.
    
    The repository manager process should not have tried to send an
    update to a non-"in use" channel. The errors resulting from this
    situation internally to the queue manager were not being handled
    correctly.
    

Problem conclusion

  • The WebSphere MQ product code will be corrected so that sending
    of updates will not be attempted via non-"in use" channels.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.11
    v9.0 LTS   9.0.0.6
    v9.1 CD    9.1.1
    v9.1 LTS   9.1.0.1
    
    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

    IT25741

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-07-18

  • Closed date

    2018-08-24

  • Last modified date

    2020-07-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PH02131

Fix information

  • Fixed component name

    IBM MQ BASE MP

  • Fixed component ID

    5724H7251

Applicable component levels

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

Document Information

Modified date:
04 July 2020