UnsatisfiedDependencyException / NoSuchBeanDefinitionException: No qualifying bean of type 'X' available
Spring couldn’t find (or choose) a bean to inject.
No qualifying bean of typerequired a bean of type Meaning
The class isn’t a Spring bean (missing @Service/@Component), it’s outside the component-scan package, an auto-configuration didn’t activate, or several beans match without a qualifier.
Common causes
- Missing @Component/@Service/@Repository
- Class outside the main application package (component scan)
- Multiple candidates without @Primary/@Qualifier
- Conditional auto-config not active (missing property/dependency)
⚡ Quick fix
- Annotate the class or declare a @Bean
- Move it under the @SpringBootApplication package
- Add @Primary or @Qualifier
Detailed fix by platform
Java
- Run with
--debugto print the auto-configuration report
How to diagnose
- Bean — Which type is missing?
- Scan — Is it in a scanned package?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- circular references The dependencies of some of the beans in the application context form a cycle
- DataSource url not specified Failed to configure a DataSource: 'url' attribute is not specified and no embedded datasource could be configured.
- HttpMessageNotReadableException HttpMessageNotReadableException: JSON parse error / Required request body is missing
Most viewed in Java
Other ways to find it
Where this error sits
Origin: Application & API. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 13 Oct 2026