Jun 18th, 2007, 02:51 AM
GlobalRollback inside nested transactions
When 'setGlobalRollbackOnParticipationFailure' of my TransactionManager is set to the default of 'true' a nested transaction (PROPAGATION_NESTED) will affect the outer transaction. This isn't what I expect but I can't tell if it is the correct behaviour or not.
My scenario is similar to the example described by JH in http://forum.springframework.org/arc...p/t-16594.html (parsing a large input file)
The main difference is that my nested transaction calls code that uses other supporting transactions. As soon as one of these inner-most transactions fails the whole lot gets rolled back. All of the exception handling seems to be done in the correct place as even if one nested transactions fails the outer transaction continues with no problem - it just rolls back when it finishes!
If I disable global rollbacks everything works fine but I don't like changing the default in case it does affect something else.
Any help appreciated :-)
Jun 18th, 2007, 12:02 PM
As explained here : http://static.springframework.org/sp...ailure(boolean)
If "setGlobalRollbackOnParticipationFailure" is "true", "the transaction will be globally marked as rollback-only. The only possible outcome of such a transaction is a rollback: The transaction originator cannot make the transaction commit anymore."
So that seems a perfectly correct behavior to me.
Jun 18th, 2007, 05:40 PM
In the same comment below it mentions that..
"The recommended solution for handling failure of a subtransaction is a "nested transaction", where the global transaction can be rolled back to a savepoint taken at the beginning of the subtransaction."
I had hoped that any inner transaction of the nested transaction would only affect this nested transaction.
Since this isn't the case, the nested transaction just becomes a normal supporting transaction -- ie. savepoints only work if there are no further inner transactions. Have I understood this correctly?