l81893521 opened a new issue, #7623: URL: https://github.com/apache/incubator-seata/issues/7623
### Check Ahead - [x] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. - [x] I am willing to try to implement this feature myself. ### Why you need it? 1. Background & Problem Currently, in both the Seata client and server components, various modules (such as TM, RM, TC, Netty RPC, etc.) independently create and manage their own thread pools using new ThreadPoolExecutor(...). This decentralized approach presents several limitations: Maintenance Difficulty: Thread pool configurations (core size, max size, queue type, rejection policy, etc.) are scattered throughout the codebase, making them hard to manage, optimize, and audit consistently. Technical Debt: With the evolution of Java, particularly the introduction of virtual threads in Project Loom (Java 21+), the current hard-coded approach creates a significant barrier to adoption. It would be extremely cumbersome to migrate all existing platform thread pools to virtual threads without a single point of control. Inconsistency: It's challenging to enforce best practices (like standardized thread naming for monitoring) and ensure consistent behavior across all thread pools and different Java versions. ### How it could be? _No response_ ### Other related information _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
