Question

In my Spring application I have service-layer methods marked as @Transactional(propagation=Propagation.REQUIRED) and am using <tx:annotation-driven />. Normally the default behavior of automatically committing the transaction when the method completes works like a charm. But in the particular case, I need to commit shortly before the end of the method – yes, even if the parts that come after that point throw an exception.

Is there a way inside such a method to get access to the current transaction? I tried this:

TransactionDefinition td = new DefaultTransactionDefinition(TransactionDefinition.PROPAGATION_MANDATORY); // make sure we're talking about the same transaction already provided by the annotation
TransactionStatus status = transactionManager.getTransaction(td);

// perform various JDBC operations

transactionManager.commit(status);
methodThatNeedsToBeCalledAfterCommit();

But looking through my logs, I only see “AbstractPlatformTransactionManager.processCommit(752) | Initiating transaction commit” occurring once, and from the timestamps this appears to be after methodThatNeedsToBeCalledAfterCommit(), which would be the normal behavior for @Transactional methods.

Is there a way to actually force a commit inside such a method?

Answer 1

I don’t think so. Moreover, Spring will try to recommit at the end of your method.
So 2 commits : bad.

You should rethink the organization of your methods.
Maybe divide the existing one in 2 methods : one with @Trnasactional, the other with your remaining lines.