IBM Support

IV17360: WMQ XMS POISON MESSAGE PROCESSING ERRONEOUSLY LEAVES MESSAGE IN AN UNCOMMITTED STATE AT APPLICATION TERMINATION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An asynchronous consumer is subscribed for a topic where
    a BOQueue and BOTHRESH are defined for that destination. When
    the consumer tries to receive the message XMS client
    intentionally make's it a poison message by not acknowledging
    the message on receipt.
    Once the BOTHRESH is reached the message appears on the BOQUEUE
    but in an uncommitted state. When the application exits the
    message returns to the destination queue. So even after matching
    backout count to BOTHRESH for the message it is not moved to the
    BOQUEUE.
    Once the message backout count matches the BOTHRESH value
    set on the destination the message it should be moved to the
    backout queue successfully in a committed state.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    XMS .Net users connecting to WMQ and taking advantage of XMS
    poison message handling.
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    Once the BOTHRESH is reached the message appears on the BOQUEUE
    but in an uncommitted state. When the application exits the
    message returns to the destination queue. So even after matching
    backout count to BOTHRESH for the message it is not moved to the
    BOQUEUE. Poison message is not moved to the backout queue when
    application running with the Client ack session in pub-sub mode
    with durable subscription.
    

Problem conclusion

  • Even while using a non-transacted session,all the message
    requeue attempts must be performed under syncpoint.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV17360

  • Reported component name

    MSG SRVCS CL .N

  • Reported component ID

    5724M2100

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-03-15

  • Closed date

    2012-04-27

  • Last modified date

    2012-04-27

  • 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

    MSG SRVCS CL .N

  • Fixed component ID

    5724M2100

Applicable component levels

  • R200 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCRTPP","label":"SupportPac"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
27 April 2012