We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Java SDK (apache/dubbo)
How do I enable the virtual thread function in 3.3? Or you can have a document address I didn't find it in the documentation
No response
The text was updated successfully, but these errors were encountered:
In Java 19 and 20, try Executors.newVirtualThreadPerTaskExecutor
@Configuration public class DubboConfig { @Bean public ExecutorService virtualThreadExecutor() { return Executors.newVirtualThreadPerTaskExecutor(); } }
dubbo: protocol: name: dubbo port: 20880 dispatcher: all threadpool: cached # 关键配置:使用虚拟线程 executor: virtualThreadExecutor
Sorry, something went wrong.
In Java 19 and 20, try Executors.newVirtualThreadPerTaskExecutor @configuration public class DubboConfig { @bean public ExecutorService virtualThreadExecutor() { return Executors.newVirtualThreadPerTaskExecutor(); } } dubbo: protocol: name: dubbo port: 20880 dispatcher: all threadpool: cached # 关键配置:使用虚拟线程 executor: virtualThreadExecutor
@configuration public class DubboConfig { @bean public ExecutorService virtualThreadExecutor() { return Executors.newVirtualThreadPerTaskExecutor(); } } dubbo: protocol: name: dubbo port: 20880 dispatcher: all threadpool: cached # 关键配置:使用虚拟线程 executor: virtualThreadExecutor
是否可以兼容springboot的yml虚拟线程开关呢 在dubbo-spring-boot-starter里 这样是可以兼容jdk17和jdk21的只需要一个开关
#15158
dubbo: protocol: name: dubbo port: 20880 threadpool: virtual
上面说的配置不对 直接配线程池类型为虚拟线程即可
No branches or pull requests
Pre-check
Search before asking
Apache Dubbo Component
Java SDK (apache/dubbo)
Descriptions
How do I enable the virtual thread function in 3.3?
Or you can have a document address
I didn't find it in the documentation
Related issues
No response
Are you willing to submit a pull request to fix on your own?
Code of Conduct
The text was updated successfully, but these errors were encountered: