-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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
When virtual threads are enabled, configure Spring Integration's task scheduler to use them #41188
Comments
Ah, hm, So I guess we should make The workaround for now is to add |
@mhalbritter However, even when adding the following configuration, @Configuration
@EnableScheduling
class ScheduleConfig Is there a priority issue? Additionally, as mentioned in the initial question, the executor assigned to Should I provide a sample for verification? |
Yes, please. |
p.s. Even though I'm not using SockJS, I noticed that It wasn't there in version 3.3.0, but it appears in version 3.3.1. I don't understand the reason for this change. |
It seems that the reason
|
The However, due to the various Beans declared in Spring's
I'm adding this comment here because I'm unsure where to raise this issue. |
In the PR below, WebSocketMessagingAutoConfiguration has been modified to use a virtual thread executor
Upon checking the taskExecutors being injected, it is taskScheduler.
When used with spring-integration, the following Bean is being configured first.
Is it possible to modify it to allow for auto-configuration?
Below is the configuration added without using auto-configuration.
Of course, the bottom properties are also set.
The text was updated successfully, but these errors were encountered: