New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scheduling auto-configuration backs off with @EnableWebSocket #28449
Comments
Thanks for the report. Unfortunately, I'm not sure what we can do about this. Even if you configure every SockJS registration with a From a Spring Boot perspective at least, it's a bit unfortunate that the SockJS support uses a I'll flag this for team attention so that we can discuss our options. @rstoyanchev, your input would be very welcome here as well please. |
|
Unfortunately, we won't be able to do that as conditions are evaluated on bean definitions, not instances and the only way for us to know would be to instantiate the bean. |
Unfortunately, we don't think there's much we can do here in the Boot 2.x timeframe without a change in Framework that will probably have to wait till 6.0 (Boot 3.0). The simplest workaround that allows the @Bean
public ThreadPoolTaskScheduler taskScheduler(TaskSchedulerBuilder builder) {
return builder.build();
} I've opened spring-projects/spring-framework#27903 to track the Framework change. In the meantime, using the auto-configured builder to define your own |
When use
@EnableWebSocket
and@EnableScheduling
at the same time,spring.task.sheduling*
will not effectAfter I debug a simple empty project, I found
ScheduledTaskRegistrar
always uselocalExecutor
, becauseTaskSchedulingAutoConfiguration.taskScheduler(TaskSchedulerBuilder builder)
not run.I guess there are some conflict codes in
WebSocketConfigurationSupport
withTaskSchedulingAutoConfiguration
The text was updated successfully, but these errors were encountered: