IBM Support

IT13527: ASYNCHRONOUS CONSUMERS MATCHING BY MESSAGE TOKEN WITH WEBSPHERE MQ EXPERIENCE LONG RESPONSE TIMES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Noticeable delays of over 5 seconds when asynchronous consumers
    consume messages from a WebSphere MQ queue using the match
    option
    MQMO_MATCH_MSG_TOKEN.
    

Local fix

  • Set the SHARECNV attribute on the SVRCONN channel to 0, or if
    using an MDB,
    set the provider version property on the Activation
    Specification to "6" to force the V6
    migration mode to be used.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users who use message matching option MQMO_MATCH_MSG_TOKEN
    either directly, or via an MQ JMS activation specification or
    listener port client may be affected by this issue.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    WebSphere MQ was incorrectly allowing applications that consume
    messages via the asynchronous consume mechanism to be made
    eligible to wait for messages if they used the
    MQMO_MATCH_MSG_TOKEN match option.
    
    This problem has the potential to cause messages to remain on
    the queue even if there are other eligible consumers to deliver
    those messages to.
    

Problem conclusion

  • The code has been modified so that applications that consume
    messages via the asynchronous consume mechanism may not be added
    to the list of eligible waiters for a queue if they have used
    the MQMO_MATCH_MSG_TOKEN match option.
    
    If a message that would match the message token is already
    available on the queue when the MQGET occurs then it is still
    delivered to the client but the client asynchronous consumer is
    suspended and the callback will receive MQRC_MSG_TOKEN_ERROR.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.7
    
    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

    IT13527

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7241

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-01

  • Closed date

    2016-04-29

  • Last modified date

    2016-04-29

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

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

    PI61671

Fix information

  • Fixed component name

    WMQ BASE MULTIP

  • Fixed component ID

    5724H7241

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
29 April 2016