Transaction Rollback on Exceptions

Understanding how Spring manages transaction rollback on exceptions is essential for building reliable applications. In this chapter, you will learn how Spring decides whether to roll back or commit a transaction when an exception occurs during transactional code execution.

How Spring Determines Transaction Rollback or Commit Based on Exception Types

Spring uses a combination of internal logic and metadata from the @Transactional annotation to decide whether to rollback or commit a transaction when an exception occurs. This process is not simply a matter of checking the exception type; it involves several steps and configurable behaviors within Spring's transaction management system.

Core Decision Process

1. Exception Detection:

   • Spring intercepts method calls marked with @Transactional.
   • If an exception is thrown during the method execution, Spring's transaction interceptor is triggered.

2. Exception Type Analysis:

   • By default, Spring rolls back on any unchecked exception (subclasses of RuntimeException or Error);
   • Spring commits the transaction for checked exceptions (subclasses of Exception that are not RuntimeException), unless specified otherwise.

3. Annotation Attributes:

   • The @Transactional annotation can override the default behavior using its rollbackFor and noRollbackFor attributes;
   • If rollbackFor includes a specific exception, Spring will roll back even if it is a checked exception;
   • If noRollbackFor includes a specific exception, Spring will commit even if it is an unchecked exception.

4. Transaction Synchronization:

   • When an exception matches the rollback criteria, Spring marks the current transaction as rollback-only;
   • If the exception does not match, Spring allows the transaction to proceed to commit.

5. Commit or Rollback Execution:

   • At the end of the method, Spring checks the transaction status;
   • If marked as rollback-only, Spring triggers a rollback;
   • Otherwise, Spring commits the transaction.

Key Takeaways

• Spring's transaction outcome is determined by both the exception type and the configuration in @Transactional;
• The process is managed internally by interceptors and rule-checking mechanisms, not by simple exception type checks;
• You can always customize rollback behavior using annotation attributes to meet your application's needs.