You are currently viewing Understanding BeanCurrentlyInCreationException in Spring Boot

Understanding BeanCurrentlyInCreationException in Spring Boot

In the realm of Spring Boot applications, developers often encounter various exceptions, each carrying its own significance and requiring a unique approach for resolution. One such exception is the BeanCurrentlyInCreationException, which can be quite puzzling for developers. In this article, we’ll delve into what this exception signifies, explore its common causes, and provide solutions to mitigate it, accompanied by relevant examples.

What is BeanCurrentlyInCreationException?
BeanCurrentlyInCreationException is a runtime exception that occurs during the initialization phase of Spring beans. It indicates that the container is trying to create a bean that is currently being created by the same container. In other words, it’s a circular dependency issue where beans depend on each other in a loop during their instantiation process, causing a deadlock situation.

Common Causes:

  1. Circular Dependency: One of the primary causes of BeanCurrentlyInCreationException is circular dependency between Spring beans. This happens when Bean A requires Bean B, and Bean B requires Bean A, directly or indirectly, forming a cyclic dependency chain.
  2. Incorrect Bean Scopes: Misconfiguration of bean scopes can also lead to this exception. For instance, if a singleton bean tries to inject a prototype bean, and the prototype bean, in turn, tries to access the singleton bean during its creation, it can result in a circular dependency and trigger the exception.
  3. Asynchronous Bean Creation: In scenarios where beans are created asynchronously, especially in multithreaded environments, the timing of bean initialization can become unpredictable, potentially leading to circular dependency issues and BeanCurrentlyInCreationException.


  1. Dependency Injection Refactoring: Analyze the dependency graph of your Spring beans and refactor the code to break any circular dependencies. Consider introducing interfaces or breaking down beans into smaller, more focused components to minimize interdependence.
  2. Lazy Initialization: Utilize lazy initialization for beans wherever applicable. Lazy initialization delays the instantiation of beans until they are actually needed, reducing the likelihood of circular dependencies during the application startup phase.
  3. Qualifiers and Primary Beans: Implement qualifiers and designate primary beans to explicitly specify dependencies and avoid ambiguous bean resolutions. This helps Spring to resolve dependencies accurately, mitigating the risk of circular dependencies.
  4. Constructor Injection: Prefer constructor injection over field or setter injection, as it can help in detecting circular dependencies at compile time rather than runtime. Constructor injection also enforces the creation of all required dependencies during bean instantiation, reducing the chances of circular dependencies.

Consider a scenario where we have two classes, UserService and EmailService, with a circular dependency between them.

public class UserService {
    private final EmailService emailService;

    public UserService(EmailService emailService) {
        this.emailService = emailService;

public class EmailService {
    private final UserService userService;

    public EmailService(UserService userService) {
        this.userService = userService;

To resolve this circular dependency, we can refactor the code to eliminate the dependency between UserService and EmailService. Alternatively, we can introduce an interface and refactor the code to break the circular dependency.

BeanCurrentlyInCreationException in Spring Boot indicates a circular dependency issue that requires careful analysis and resolution. By understanding the common causes and applying appropriate solutions such as dependency injection refactoring, lazy initialization, and constructor injection, developers can effectively mitigate this exception and ensure the smooth initialization of Spring beans in their applications.

Leave a Reply