Avoiding Redelivery Loops in JMS Local Transactions

  GigaSpaces 5.X

Documentation Home
Quick Start Guide
Release Notes

Previous release

  Search Here
Searching GigaSpaces Platform 5.X Documentation

                                               

Summary: It is recommended not to use an application that rolls back the transaction when an error happens.

Overview

When many messages are consumed within a local transaction and the transaction in reaction is rolled back, the JMS provider redelivers them immediately. If the rollback happened because the message was somehow corrupted, the message will probably be rolled back again. The above scenario can repeat indefinitely with the same message recurrently rolled back and redelivered. Therefore, it is recommended not to use an application that rolls back the transaction when an error happens. It is better that the application handle such an error differently and commit the transaction normally.


Wiki Content Tree


Your Feedback Needed!

We need your help to improve this wiki site. If you have any suggestions or corrections, write to us at techw@gigaspaces.com. Please provide a link to the wiki page you are referring to.

Labels

 
(None)