IBM Support

IT10170: JMS PUBSUB MESSAGE SELECTOR LOST AFTER MULTI-INSTANCE QUEUE MANAGER FAILOVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After a multi-instance queue manager failover, an IBM MQ v8
    classes for JMS application using the Automatic Client Reconnect
    feature stops honouring the configured message selection string
    when consuming messages from a Topic destination.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects all users of the:
    
      - WebSphere MQ v7.1 classes for JMS
      - WebSphere MQ v7.1 classes for Java
    
      - WebSphere MQ v7.5 classes for JMS
      - WebSphere MQ v7.5 classes for Java
    
      - IBM MQ v8 classes for JMS
      - IBM MQ v8 classes for Java
    
    who use a message selection string when consuming messages from
    a Topic destination with an application configured to use the
    Automatic Client Reconnect function.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    As an example, an IBM MQ classes for JMS application can specify
    a message selector when creating a MessageConsumer such that
    only messages matching the selection String are consumed by the
    application. Such a MessageConsumer can be created, for example,
    using a call to:
    
      javax.jms.Session.createConsumer(Destination, String, boolean)
    
    where the second parameter is the message selection expression.
    
    If an IBM MQ classes for JMS application consumed messages from
    a Topic destination using a message selector and the Automatic
    Client Reconnect function was invoked, for example because a
    multi-instance queue manager failed over or the queue manager to
    which it was connected to was stopped using the "endmqm -r"
    command, then the IBM MQ classes for JMS would attempt to
    reestablish connectivity to other queue managers it has been
    configured with (via a Client Channel Definition Table, CCDT, or
    the JMS Connection Factory property CONNECTIONNAMELIST). After
    the connection was reestablished, the message selector
    originally used to create the MessageConsumer would no longer be
    honoured. As a result, any messages that were published to the
    Topic destination would then be consumed by the application,
    including those not matching the specified selection expression.
    
    The same issue existed when consuming message from a Topic
    destination using the classes for Java API.
    

Problem conclusion

  • The WebSphere MQ classes for JMS, WebSphere MQ classes for Java,
    IBM MQ classes for JMS and IBM MQ classes for Java have been
    updated such that, for Topic destinations, subscriptions created
    after Automatic Client Reconnection occurs matches that of the
    initial subscription with regard to message selectors, thereby
    ensuring that the application continues to receive only messages
    which match the selector specified.
    
    See APAR IV33459 for the equivalent change in MQ 7.0.1
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.8
    v7.5       7.5.0.6
    v8.0       8.0.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

    IT10170

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-07-17

  • Closed date

    2015-08-25

  • Last modified date

    2015-12-07

  • 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

    WMQ BASE MULTIP

  • Fixed component ID

    5724H7251

Applicable component levels

  • R800 PSY

       UP

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

Document Information

Modified date:
07 December 2015