Troubleshooting Null @Autowired Values in Java Spring Boot

Published on 2024.02.12


One of the key features of the Spring framework is dependency injection, which allows developers to define and manage the relationships between different components in a Java application. With Spring Boot, this capability is taken further by providing auto-configuration and component scanning, making it easy to build production-ready applications.

However, it is not uncommon to encounter issues where the values of @Autowired dependencies are null, causing NullPointerExceptions and unexpected behavior in the application. In this article, we will explore some common reasons for this problem and provide actionable solutions.

Issue: Incorrect Configuration

One possible reason for having null @Autowired values is incorrect configuration. This can occur when the component you are trying to inject is not declared correctly or is not included in the component scan. To troubleshoot this, you can:

  • Check if the component is annotated with @Component or other relevant stereotype annotations.
  • Verify that the component is included in the component scan. You can do this by checking your configuration class or configuration XML file.

Issue: Multiple Implementations

Another possible cause of null @Autowired values is having multiple implementations of the dependency. When there are multiple candidates that match the type of the dependency, Spring might not be able to determine which one to inject, resulting in a null value. To fix this issue, you can:

  • Use @Qualifier annotation along with @Autowired to specify the exact implementation to inject.
private MyInterface myInterface;
  • Use @Primary annotation on one of the implementations to indicate the default one to be used if no qualifier is specified.
public class MyPrimaryImplementation implements MyInterface {
    // ...

Issue: Circular Dependencies

Circular dependencies occur when two or more components depend on each other. This can result in null @Autowired values because Spring cannot resolve the circular dependency. To resolve this, you can:

  • Refactor your code to remove the circular dependency. Consider extracting common functionality into a separate class or using event-driven architecture.
  • Use constructor injection instead of field injection. Constructor injection can help break the circular dependency.
public MyClass(MyDependency myDependency) {
    this.myDependency = myDependency;

Issue: Bean Not Created

If the dependency you are trying to inject is not a Spring-managed bean, Spring will not be able to autowire it. To fix this issue, you can:

  • Annotate the dependency class with appropriate stereotype annotations, such as @Component, @Service, @Repository, or @Controller.
  • Add the dependency class to the component scan.
  • Explicitly create a bean definition for the dependency in your configuration class or XML file.


Null @Autowired values can be frustrating and can lead to unexpected errors in a Spring Boot application. By understanding the common causes and taking the appropriate actions, you can troubleshoot and fix these issues. Remember to ensure correct configuration, handle multiple implementations, resolve circular dependencies, and create beans for non-managed dependencies. Happy coding!