Custom AsyncConfigurer no longer taken into account when upgrading to Spring Boot 3.5

[rayliang123]

Springboot3.5.0, it added this code, but I customized an AsyncConfigurer implementation, @ConditionalOnMissingBean will be invalid, and AsyncConfigurerConfiguration.AsyncConfigurer will be added to the spring container anyway, so that the container has two AsyncConfigurer implementation classes, one is self-customized, and the other is provided by pringboot, which will report an error when starting.

Excuse me, how to solve it? I don’t want the AsyncConfigurer implementation that comes with the framework.

[bclozel]

This probably means your custom bean hasn't been considered. Rather than providing screenshots of the Spring Boot codebase, a minimal sample application would help us to find the actual problem. Please provide a minimal sample application.

[mymx2]

use @AutoConfiguration(before = {org.springframework.boot.autoconfigure.task.TaskExecutionAutoConfiguration.class})

[spring-projects-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

[spring-projects-issues]

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.