You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use an AsyncConfigurer that needs some beans. Spring wants to create a BeanPostProcessor asyncAdvisor at org.springframework.scheduling.annotation.ProxyAsyncConfiguration. This bean post processor uses the instance variables this.executor and this.exceptionHandler
all AsyncConfigurer are autowired to ProxyAsyncConfiguration via the following method
snicoll
changed the title
AbstractAsyncConfiguration -> prelimary instance creation before method call setConfigurers(Collection<AsyncConfigurer> configurers)
AsyncConfigurer implementations are loaded too early
Dec 14, 2021
Affects: 5.3.3
We use an
AsyncConfigurer
that needs some beans. Spring wants to create a BeanPostProcessorasyncAdvisor
atorg.springframework.scheduling.annotation.ProxyAsyncConfiguration
. This bean post processor uses the instance variablesthis.executor
andthis.exceptionHandler
all AsyncConfigurer are autowired to ProxyAsyncConfiguration via the following method
org.springframework.scheduling.annotation.AbstractAsyncConfiguration
This leads to a prelimary instance creation of all asyncConfigurer and its dependent beans.
IMHO this should be changed to use an ObjectProvider instead:
method evaluateAsyncConfigurer() should be called before access to this.executor and this.exceptionHandler in child classes.
The text was updated successfully, but these errors were encountered: