1.

Does Jms Specification Define Transactions? Queue

Answer»

JMS specification defines a transaction mechanisms allowing clients to SEND and receive groups of logically BOUNDED messages as a single unit of information. A Session may be MARKED as transacted. It means that all messages sent in a session are considered as parts of a transaction. A set of messages can be committed (commit() method) or rolled back (ROLLBACK() method). If a provider supports DISTRIBUTED transactions, it's recommended to use XAResource API. 

 

JMS specification defines a transaction mechanisms allowing clients to send and receive groups of logically bounded messages as a single unit of information. A Session may be marked as transacted. It means that all messages sent in a session are considered as parts of a transaction. A set of messages can be committed (commit() method) or rolled back (rollback() method). If a provider supports distributed transactions, it's recommended to use XAResource API. 

 



Discussion

No Comment Found