IBM Support

IT14031: MDB using MCA Interception stops consuming messages after a poison message is encountered

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An Activation Specification endpoint running within a Java
    Enterprise Edition (JEE) application server environment, such as
    WebSphere Application Server, is configured to consume messages
    from a WebSphere MQ queue.  The client/server channel has been
    protected by MCA Interception.
    
    The queue contains a message which has MQMD.BackoutCount which
    exceeds the BackoutThreshold (BOTHRESH) defined on the queue.
    
    After one of the messages is processed by the Activation
    Specification and moved to the backout queue, no more messages
    are consumed by the Activation Specification, even though there
    are messages available on the queue.
    
    No error messages are observed in the application server logs,
    and the activation specification continues to be listed as
    active.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users having JEE applications implemented via MDBs, consuming
    from MQ queues on a queue manager that has been set up to use
    MCA Interception.
    
    This problem might also affect other non-Java clients using
    asynchronous consume from MQ queues on a queue manager that has
    been set up to use MCA Interception.  However no problem in this
    scenario has been reported to IBM
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    During backout-requeue processing ("poison message processing")
    of the message in the scenario described, the MQ JMS code within
    the MDB was required to get the message using different options
    from the normal options used by the MDB in normal processing.
    
    These different options were being stored by the part of the
    queue manager that performs async consume functions, and were
    causing future async consume to fail.  The different options
    should not have been stored by the queue manager and used in
    this way.
    

Problem conclusion

  • The MQ queue manager code has been corrected.  The different
    options used during backout-requeue processing are no longer
    stored and used on subsequent async consume functions.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.7
    v8.0       8.0.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

    IT14031

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7241

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-29

  • Closed date

    2017-01-24

  • Last modified date

    2017-01-24

  • 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

    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:
24 January 2017