IBM Support

IT25883: Misleading message produced during backout processing

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 written to the IBM MQ classes for JMS log as a result
    of a failure to move a message to either a specified backout
    queue or the dead letter queue contain misleading or incomplete
    information
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects environments where the IBM MQ classes for JMS
    are unable to re-queue messages to a specified backout queue or
    dead-letter queue
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When an attempt by the IBM MQ classes for JMS to re-queue a
    message either to a specified backout queue, or to the queue
    manager's dead-letter queue failed - for instance because the
    queue was full, or the queue's authority settings prevented this
    - there would either be no message written to the log at all to
    inform the user of this failing re-queue attempt, or the message
    that was written contained either misleading information or not
    enough information to identify the message or the queue to which
    the re-queue failed.
    
    For instance, if an attempt to re-queue a message to a specified
    backout queue failed, there was no message written to the log to
    inform the user of this.
    
    If an attempt to re-queue a message to the dead-letter queue
    failed, a message was written to the log informing the user of
    this, and the exception that caused the failure - however there
    was nothing in the message logged to allow the user to identify
    the message involved. Also, the message written to the log would
    have a misleading linked exception containing the message
    "JMSWMQ1080: No Backout-Requeue queue defined".
    

Problem conclusion

  • When an attempt by the IBM MQ classes for JMS to re-queue a
    message either to a specified backout queue, or to the queue
    manager's dead-letter queue fails, a message is written to the
    log indicating the message ID of the message, the name of the
    backout or dead-letter queue the message could not be moved to,
    and the exception or error that prevented the move.
    
    A failure to move a message to the backout queue will result in
    a log message:
    
    JMSWMQ1120 = Message "{message ID}", could not be moved to
    backout queue "{backout queue name}" for reason "{exception or
    error}", it will be moved to the dead letter queue or discarded.
    
    A failure to move a message to the dead-letter queue will result
    in a log message:
    
    JMSWMQ0035 = Message "{message ID}", could not be moved to dead
    letter queue "{dead-letter queue name}" because of exception
    "{exception or error}", it will be returned to the source queue.
    
    If there is an exception listener registered on a consumer which
    tries and fails to re-queue a message to the dead-letter queue,
    as well as the log message being written an exception will be
    sent to this exception listener. This exception will now contain
    the exception message text:
    
    JMSWMQ1079: Unable to write a message to dead letter queue.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.11
    v9.0 LTS   9.0.0.6
    v9.1 CD    9.1.2
    v9.1 LTS   9.1.0.2
    
    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

    IT25883

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-08-02

  • Closed date

    2018-10-24

  • Last modified date

    2018-11-16

  • 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

    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:
16 November 2018