IBM Support

IC68194: EVENT SEQUENCING DOES NOT DISABLE REDELIVERY OF FAILED MESSAGES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Generated Activation Specs for MQ and MQ/JMS exports do not
    disable redelivery of failed messages when Event Sequencing is
    enabled in the binding.  Since MQ does not preserve message
    order with redelivery of failed messages this causes messages
    order to be broken.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Customers using WebSphere Enterprise         *
    *                 Service Bus and WebSphere Process Server     *
    *                 v7.0 to generate Activation Specs for MQ     *
    *                 and MQ/JMS exports may find that             *
    *                 redelivery of failed messages is not         *
    *                 disabled.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: By default, when the Activation Spec    *
    *                      for MQ and MQ/JMS exports is created,   *
    *                      the setting "disable Failed Message     *
    *                      Redelivery" is set to false. This       *
    *                      means that redelivery will be           *
    *                      attempted, causing the message order    *
    *                      held in MQ to be broken.                *
    ****************************************************************
    * RECOMMENDATION: If you require message order to be           *
    *                 preserved when using MQ or MQ/JMS exports    *
    *                 then you are advised to install the fix      *
    *                 pack which contains the code update          *
    *                 associated with this APAR.                   *
    ****************************************************************
    Generated Activation Specs for MQ and MQ/JMS exports do not
    disable redelivery of failed messages when Event Sequencing is
    enabled in the binding.  Since MQ does not preserve message
    order with redelivery of failed messages this causes messages
    order to be broken.
    
    The change in this APAR will mean that when creating the
    Activation Spec when Event Sequencing is enabled the setting
    "disable Failed Message Redelivery" will be set to true.
    
    
    The behaviour will then be that the listener will stop and the
    message will be rolled back to the queue on first failure.
    

Problem conclusion

  • The code has been modified so that the listener will stop and
    the message will be rolled back to the queue on first failure.
    
    This code fix was targeted to be included in the following fix
    packs:
          7.0.0 Fix Pack 3 (v7.0.0.3)
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC68194

  • Reported component name

    WEB ESB FOR WIN

  • Reported component ID

    5724I8200

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-28

  • Closed date

    2010-07-29

  • Last modified date

    2010-07-29

  • 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

    WEB ESB FOR WIN

  • Fixed component ID

    5724I8200

Applicable component levels

  • R100 PSN

       UP

  • R200 PSN

       UP

  • R300 PSN

       UP

  • R612 PSN

       UP

  • R620 PSN

       UP

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7J6S","label":"WebSphere Enterprise Service Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
30 March 2023