How does @Transactional work, and why can self-invocation bypass it?

Explains Spring's transactional proxy boundary and why an internal method call does not normally start independent advice.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Spring normally implements @Transactional with an AOP proxy around a managed bean. A call from another bean goes through that proxy, which asks the transaction manager to start, join, suspend, commit, or roll back a transaction around the method. A call from one method to another on the same object uses this and does not cross the proxy, so the inner method's separate transactional annotation is not intercepted in the usual proxy mode.

Full answer below

Practice focus

AOP proxies, method interception, self-invocation, visibility, transaction managers, and testable boundaries.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
In the common proxy mode, transaction behavior applies when a call crosses the Spring proxy.
Spring normally implements @Transactional with an AOP proxy around a managed bean. A call from another bean goes through that proxy, which asks the transaction manager to start, join, suspend, commit, or roll back a transaction around the method. A call from one method to another on the same object uses this and does not cross the proxy, so the inner method's separate transactional annotation is not intercepted in the usual proxy mode.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
This is especially dangerous when the inner method declares REQUIRES_NEW, different isolation, or read-only behavior and the developer assumes it took effect. Moving the transactional operation to another focused bean makes the boundary explicit; restructuring the public entry method is often clearer than injecting the bean into itself. Private methods are not useful proxy boundaries in common proxy-based designs. Tests should assert actual commit and rollback behavior, not merely inspect annotations.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Assuming every annotated call starts a transaction.
Putting REQUIRES_NEW on a self-invoked helper.
Testing transaction behavior with mocks only.

How does @Transactional work, and why can self-invocation bypass it?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue the section

Tech stacks

Skill areas

Suggest an improvement

Found this answer useful?