IBM Support

IT40791: IBM MQ Classes for JMS - Messages are not going to the backout queue after the backout threshold is hit.

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

  • Messages are not going to the backout queue after the backout
    threshold is reached. The IBM MQ classes for JMS appears to be
    receiving the error MQRC 2097 (MQRC_CONTEXT_HANDLE_ERROR) - It
    cannot put the message onto the backout queue nor the dead
    letter queue. Instead the message is just rolled back again.
    This occurs when durable JMS Subscriptions are used.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of MQ Classes for JMS, with Asynchronous message
    consumers, connecting to a topic with a backout threshold
    defined.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Messages are not going to the backout queue after the backout
    threshold is reached. The IBM MQ classes for JMS appears to be
    receiving the error MQRC 2097 (MQRC_CONTEXT_HANDLE_ERROR) - It
    cannot put the message onto the backout queue nor the dead
    letter queue. Instead the message is just rolled back again.
    
    An FFST/FFDC is typically generated when encountering this
    behaviour, detailing reason code 2097.
    

Problem conclusion

  • Context is now set correctly for an Asynchronous message
    consumer when initialised for a topic/subscription. This enables
    the message to be successfully moved to a defined backout queue.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.12
    v9.2 LTS   9.2.0.7
    v9.3 LTS   9.3.0.1
    v9.x CD    9.3.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

    IT40791

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-04-29

  • Closed date

    2022-05-10

  • Last modified date

    2022-09-30

  • 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 MP

  • Fixed component ID

    5724H7271

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
30 September 2022