JMS Local Transactions

Added by Gilad David Maayan, last edited by Aleia Hutcherson on May 26, 2008  (view change)
  GigaSpaces 5.X

Documentation Home
Quick Start Guide
Release Notes

Previous release
  Search Here
Searching GigaSpaces Platform 5.X Documentation

                                               
Summary: Starting, committing, rolling back; sending/consuming messages under local transaction; avoiding redelivery loops.

Overview

A transaction lets you send or consume a set of messages in one operation. The effect is that either all or none of the messages are processed.
If messages are produced in a transaction, the messages are only sent or published when the transaction is committed. If the transaction is rolled back, all messages sent or published inside the transaction are not delivered and become discarded.

Whenever messages are consumed in a transaction, the client only acknowledges the consuming of these messages when the transaction is committed. But if the transaction is rolled back, the messages are not acknowledged.

The GigaSpaces Real Time Data Bus supports both local and global transactions. The following section explains about local transactions. A local transaction is the simpler of the two since it only involves messages produced and consumed within the session alone. In contrast, a global transaction can include multiple JMS sessions together with multiple databases.

Support for local transactions in the GigaSpaces Real Time Data Bus is implemented using the native facilities of the underlying messaging product. If such products do not support transactions, the GigaSpaces Real Time Data Bus framework itself will support them.

More in this Section

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)