I\'m using java config with @ComponentScan
in order to initialize my beans
and @EnableAspectJAutoProxy(proxyTargetClass=true)
to use cglib proxies.
Finally I sorted it out using @Lazy
on services (with methods annotated with @Async
), and also, where they were autowired.
This way I guess Spring only initialize and autowires those services when they're required instead of on application context initialization.
I have same issue and I solved this issue:
I identified which @Autowired
property is reason for circular dependency.
Eg:
@Autowired
private TestService testService;
(Tips to identified just try to comment and find out which property is reason to break the application)
Once identified just use @Lazy
on top of this @Autowired
variable.
Eg :
@Lazy
@Autowired
private TestService testService;
And Application worked smoothly.
I managed to fix a similar issue by adding @Qualifier together with @Autowire, for example:
@Autowired
@Qualifier("publisher")
private Publisher publisher;
AsyncConfigurer configuration classes get initialized early in the application context bootstrap. If you need any dependencies on other beans there, make sure to declare them 'lazy' as far as possible in order to let them go through other post-processors as well.
Reference JavaDoc: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/scheduling/annotation/EnableAsync.html