[JMS_SPEC-130] Allow a JMSContext or Session to opt out of a Java EE transaction Created: 18/Jun/13 Updated: 18/Jun/13
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
The JMS 2.0 specification, section 12.3 "Behaviour of JMS sessions in the Java EE web or EJB container" states that if a Session or JMSContext is created when there is an active JTA transaction in progress then any session parameters are ignored and the Session or JMSContext will participate in the JTA transaction and will be committed or rolled back when the JTA transaction is committed or rolled back.
The specification doesn't appear to offer any choice as to whether the Session or JMSContext participates in the JTA transaction.
Issue: Should it be possible for the Session or JMSContext to "opt out" of the transaction in some way?
Here are some circumstances in which the JTA transaction might be ignored:
If the Session or JMSContext is allowed to opt out of the JTA transaction, then we could define that it behave the same way as a Session or JMSContext that is created when there is no JTA transaction (i.e. only AUTO_ACKNOWLEDGE and DUPS_OK_ACKNOWLEDGE are allowed).
However another possibility is to further extend the specification to allow client-acknowledgement or a local transactions to be used. I think that can be discussed as a separate issue and I have created JMS_SPEC-131 to cover it.