How does JMS provide local transactions?
A. Local transactions are enabled by a JMS specific API called transacted sessions. For vendors other than WebLogic JMS, the scope of a transacted session is typically limited to a single JMS server. In WebLogic JMS, multiple JMS operations on multiple destinations within an entire cluster can participate in a single transacted session’s transaction. In other words, it is scoped to a WebLogic cluster and no remote JMS provider to the JMS session’s cluster can participate in a transaction. See the WebLogic JMS Performance Guide white-paper available on the JMS topic page.
A. Local transactions are enabled by a JMS specific API called transacted sessions. For vendors other than WebLogic JMS, the scope of a transacted session is typically limited to a single JMS server. In WebLogic JMS, multiple JMS operations on multiple destinations within an entire cluster can participate in a single transacted session’s transaction. In other words, it is scoped to a WebLogic cluster and no remote JMS provider to the JMS session’s cluster can participate in a transaction.