Home › Java exceptions › BeanCurrentlyInCreationException

What it looks like

org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'orderService': Requested bean is currently in creation: Is there an unresolvable circular reference?

Extends BeanCreationException in org.springframework.beans.factory.

What it means

With constructor injection, bean A needs B to be built, and B needs A, so neither can be created first. Since Spring Boot 2.6 circular references are prohibited by default, and the startup failure prints the cycle as a diagram: A (by constructor) to B (by constructor) back to A. Older versions silently resolved field-injected cycles with early references, which hid a design problem.

Common causes

• Two services that call each other directly through constructor injection.
• A configuration class that injects a bean defined by itself indirectly.
• An aspect, listener or event handler that depends on the bean it observes.
• Growing a service until it needs the beans that need it.

How to fix it

1. Break the cycle by extracting the shared logic into a third bean that both depend on.
2. Replace one direction with an event (ApplicationEventPublisher) so the dependency is not direct.
3. Inject lazily as a last resort with @Lazy on one constructor parameter.
4. Avoid spring.main.allow-circular-references=true, which only hides the design problem.

Broken and fixed

@Service class A { A(B b) {} }
@Service class B { B(A a) {} }

@Service class A { A(Shared s) {} }
@Service class B { B(Shared s) {} }
@Service class Shared { }

🔎 Unravel the failing code 🔎 Unravel the fix

Debug it faster

Paste the whole stack trace into the stack trace beautifier to hide framework frames, jump to the root cause and find the first line of your own code. It runs in your browser, so the trace never leaves your machine.

Related exceptions