IBM Support

IT27273: MQ Client Applications configured for reconnection do not reconnect when the Queue Manager fails over using MSCS.

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

  • Applications that are configured for reconnection do not
    reconnect to the queue manager when Microsoft Cluster Server
    (MSCS) is used
    to fail over the queue manager resource.
    
    However, the applications successfully reconnect when the queue
    manager is ended with the -r option or the queue manager
    terminates unexpectedly.
    

Local fix

  • Ending the QM with 'endmqm -r ' will allow the automatic
    reconnect client to connect.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users with MQ client applications that connect to queue managers
    that are configured in MSCS Active - Active setup and use the
    client reconnect feature.
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    MQ applications that use a Client Connection Definition Table
    (CCDT) to connect to a group of queue managers will connect to
    the next available queue manager if the existing connection
    fails and if client auto reconnect is enabled.  If a queue
    manager is configured to run under MSCS active-active
    configuration then during failover the client reconnection
    fails.
    
    This is because the queue maanager follows pre-emptive shutdown
    during a failover and hence the application fails to reconnect
    once the queue manager becomes active on the other node.
    

Problem conclusion

  • Code has been modified such that the queue manger is shutdown
    with the correct options to enable connections from
    reconnectable clients.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 LTS   9.0.0.7
    v9.1 CD    9.1.3
    v9.1 LTS   9.1.0.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

    IT27273

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-12-11

  • Closed date

    2019-06-10

  • Last modified date

    2019-06-10

  • 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 M/P

  • Fixed component ID

    5724H7261

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":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
10 June 2019