[jboss-dev-forums] [Design of JBoss Transaction Services] - Re: TransactionTimeoutConfiguration pluggability

[adrian@jboss.org]

"jhalliday" wrote : The tin actually contains no specification to cover this - it only requires that the exception is thrown if the tx is marked for rollback, not if it's actually rolled back or rolling back. Basically the interface spec does not anticipate async rollback processing. I could close the JIRA as 'this is not a bug' until the spi javadoc is revised.

The javadoc was written against the old TM behaviour it obviosuly needs updating.
RolledBack/Committed/Completed/etc. is also an error 
(only RollbackOnly was possible with the old TM).

anonymous wrote :  Or in light of your comment here, I could throw away the JBossTS implementation of TransactionTimeoutConfiguration and nothing in the AS would break?

Correct, except for people that expect
<set-tx-timeout/>
in the jdbc resource adapter to work like it used to.

Instead no query timeout will be set automatically (not fatal, but it is a regression
of sorts).

P.S. I've got a "feature request" open for JavaEE6 that this method or something
like it gets added to the TransactionSynchronizationRegistry (JTA spec).

* It will mean this behaviour is portable across appservers
* You'd have to implement it anyway ;-)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137799#4137799

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137799