-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
Documentation (Ref Guide, User Guide, etc.), Release Notes, Compatibility/Configuration
Add support for a traditional (JCA 1.5 Chapter 12.5.6 Option A) XA transaction model in the generic JMS resource adapter.
The default when using an XASession should be the traditional one, but the old behavior can be enabled by setting the ForceTransacted flag in the activation spec.
- relates to
-
JBPAPP-2260 Setting maxMessages > 1 results in multiple message deliveries within one transaction
- Closed