Introduction

Java Spring @Autowired injection fails when no matching bean or multiple candidates exist. This guide provides step-by-step diagnosis and resolution with specific commands and code examples.

Symptoms

Typical symptoms and error messages when this issue occurs:

bash
java.lang.Error: Unexpected error occurred
	at com.example.Application.main(Application.java:42)
Caused by: internal error

Observable indicators: - Application logs show errors or exceptions - JVM crashes or becomes unresponsive - Related services may fail or timeout

Common Causes

  1. 1.Framework issues are commonly caused by:
  2. 2.Missing or incorrect bean configuration
  3. 3.Dependency injection failures
  4. 4.Transaction management misconfiguration
  5. 5.Entity mapping errors

Step-by-Step Fix

Step 1: Check Current State

bash
java -version

Step 2: Identify Root Cause

bash
jcmd <pid> VM.info

Step 3: Apply Primary Fix

java
// Primary fix: update configuration
@Configuration
public class AppConfig {
    @Bean
    public MyBean myBean() {
        MyBean bean = new MyBean();
        bean.setTimeout(30000);
        return bean;
    }
}

Apply this configuration and restart the application.

Step 4: Apply Alternative Fix (If Needed)

java
// Alternative fix: use properties
# application.properties
app.timeout=30000
app.retry-count=3
app.enabled=true

Enable DEBUG logging for framework classes to diagnose configuration issues.

Step 5: Verify the Fix

After applying the fix, verify with:

bash
mvn spring-boot:run -Ddebug=true

Expected output should show successful operation without errors.

Common Pitfalls

  • Missing @Component or @Service annotation
  • Incorrect @Qualifier usage
  • Circular dependencies without @Lazy

Best Practices

  • Use constructor injection over field injection
  • Keep bean definitions simple
  • Profile-specific configuration
  • Java Spring Bean Creation Exception
  • Java Spring Transaction Not Rolling Back
  • Java Spring Security Access Denied