Transacted JMS Sessions

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: When isTransacted is set to true, the session is transacted and the argument acknowledgeMode is ignored.

Overview

When isTransacted is set to true, the session is transacted and the argument acknowledgeMode gets ignored.
If a transacted session produces messages, the messages are only sent or published when the session is committed with session.commit(). If the session is rolled back instead, with session.rollback(), all messages sent or published within the transaction are not delivered and instead get discarded.

When a transacted session consumes messages, the client only acknowledges that it has consumed any messages when the session is committed. If the session is rolled back instead then the messages are not acknowledged.
A transacted session only includes messages produced and consumed within the session, no others. It doesn't include messages produced or consumed in other JMS sessions, nor other resources, like databases. In the terminology of transactions, it uses a local transaction.

For more details, refer to Local Transactions.

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)