Java – Rollback all nested transactions when outer one is marked for rollback

javapropagationrollbackspringtransactions

I've got two methods annotated with @Transactional. The second method is called somewhere nested inside the first one.

Now I want the following behaviour to happen:

Every time the second, nested method is entered, a new nested
transaction should be created. When that transaction is marked for a
rollback, only that transaction should be rolled back.
But when the
transaction of the outer method is marked for a rollback, every
nested transaction inside — whether it's marked for a rollback or not —
should be rolled back.

How do I have to set the Propagation values to achieve such functionality?

P. S.: I'm using a HibernateTransactionManager.

Best Answer

You need to use NESTED. Note that this propagation mode uses JDBC SavePoints in order to achieve this behavior, and that the nested behavior thus only works if the transaction is just a wrapper around the JDBC connection. It won't work for JTA transactions. See the Spring documentation for more details.

Related Solutions

Spring – How to rollback nested transactions with Propagation.REQUIRES_NEW in integration tests

This is expected behaviour, and is one of the main reasons to use REQUIRES_NEW :

be able to rollback the new transaction, but commit the outer one
be able to commit the new transaction, but rollback the outer one

re-populate the database between tests is probably the best solution, and I would use this solution for all the tests: this allows tests to check that everything works correctly, including the commit (which could fail due to flushing, deferred constraints, etc.).

But it you really want to rollback the transaction, a solution would be to add a boolean argument rollbackAtTheEnd to your service, and rollback the transaction if this argument is true.

Spring – No rollback only for transaction when exception occurs in submethod

Create another annotation, e.g. @NoRollbackTransactional, something like:

@Transactional(noRollbackFor = RuntimeException.class)
public @interface NoRollbackTransactional {
}

And use this on your methods. On the other hand I agree with Donal's comment, you should revise your transaction scopes, imho it is generally not a good idea to call @Transactional from another @Transactional.

Best Answer

Related Solutions

Spring – How to rollback nested transactions with Propagation.REQUIRES_NEW in integration tests

Spring – No rollback only for transaction when exception occurs in submethod

Related Topic