Understanding Spring Transaction Management: @EnableTransactionManagement, Execution Principles, Propagation Mechanisms, and Forced Rollback

Enabling Spring transactions with @EnableTransactionManagement adds an Advisor to the container by registering two beans: AutoProxyRegistrar and ProxyTransactionManagementConfiguration .

AutoProxyRegistrar registers an InfrastructureAdvisorAutoProxyCreator bean, which extends AbstractAdvisorAutoProxyCreator and automatically creates proxies for beans that match an advisor.

ProxyTransactionManagementConfiguration defines three additional beans: BeanFactoryTransactionAttributeSourceAdvisor (an Advisor), AnnotationTransactionAttributeSource (the Pointcut that looks for @Transactional ), and TransactionInterceptor (the Advice that executes the transactional logic).

During bean creation, InfrastructureAdvisorAutoProxyCreator checks whether a bean or its methods are annotated with @Transactional . If a match is found, a proxy is created. When a transactional method is invoked, the proxy uses the configured PlatformTransactionManager to:

Create a database connection and set autocommit to false .

Execute the target method via MethodInvocation.proceed() .

Commit the transaction if no exception occurs, or roll back if an exception is thrown.

The propagation mechanism determines how nested transactional calls behave. The article presents four cases:

Case 1 : Both methods use the default Propagation.REQUIRED , sharing a single transaction.

Case 2 : An exception in the outer method causes the whole transaction to roll back.

Case 3 : An exception in the inner method also rolls back the outer transaction because the same transaction is used.

Case 4 : The inner method is annotated with Propagation.REQUIRES_NEW , creating a separate transaction that rolls back independently, while the outer transaction can still commit or roll back based on its own outcome.

For forced rollback within a try‑catch block, developers can call TransactionAspectSupport.currentTransactionStatus().setRollbackOnly() to mark the current transaction for rollback even if the exception is caught.

Spring also provides TransactionSynchronization callbacks (e.g., suspend , resume , beforeCommit , afterCommit , afterCompletion ) that allow custom logic to be executed at various transaction lifecycle stages. Example code registers a TransactionSynchronization implementation to log messages during these phases.

Overall, the article offers a comprehensive guide to the inner workings of Spring transaction management, including bean registration, proxy creation, execution flow, propagation strategies, forced rollback, and synchronization callbacks.