IBM Support

IV52544: AFTER AN EXCEPTION OCCURS IN AN MDB, SUBSEQUENT MESSAGES ARE INCORRECTLY ROLLED BACK BY THE WMQ RESOURCE ADAPTER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • While processing a message, a message-driven bean application
    throws an exception which results in that message being rolled
    back by the WebSphere MQ Resource Adapter. When the
    message-driven bean application processes subsequent messages,
    the WebSphere MQ Resource Adapter incorrectly rolls messages
    back even if the application does not throw an exception
    during message processing.
    .
    Additional keywords:
    roll back rollback
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - The WebSphere MQ V7 Resource Adapter.
    - The WebSphere Application Server V7 WebSphere MQ messaging
      provider.
    - The WebSphere Application Server V8 WebSphere MQ messaging
      provider.
    
    who have Message Driven Beans that may throw an Exception during
    their processing in the onMessage() method.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    When an exception is thrown by a Message Driven Bean (MDB)
    throws, the result is that the associated MDB transaction is
    marked as a failure, which leads to the transaction being rolled
    back.
    
    Depending on the sequence of actions performed by the
    Transaction Manager, the flag to indicate that the transaction
    was marked as a failure was not always reset when using the MQ
    V7 Resource Adapter.
    
    The result of this was that subsequent transactions were also
    rolled back instead of being committed, even when no failure
    occurred during that subsequent MDB processing.
    

Problem conclusion

  • The WebSphere MQ V7 Resource Adapter has been changed to reset
    the affected flag to its default value in all circumstances.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.1.12
    v7.1       7.1.0.5
    v7.5       7.5.0.4
    
    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

    IV52544

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-11-25

  • Closed date

    2013-12-20

  • Last modified date

    2014-01-13

  • 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 AIX V7

  • Fixed component ID

    5724H7221

Applicable component levels

  • R701 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
13 January 2014