RongtongJin opened a new issue, #9771: URL: https://github.com/apache/rocketmq/issues/9771
### Before Creating the Enhancement Request - [x] I have confirmed that this should be classified as an enhancement rather than a bug/feature. ### Summary In single-process multi-broker environments (such as brokercontainer), the `executorService` field in `AbstractTransactionalMessageCheckListener` class uses the `static` modifier, which causes multiple broker instances to share the same thread pool. ### Motivation In single-process multi-broker environments (such as brokercontainer), the `executorService` field in `AbstractTransactionalMessageCheckListener` class uses the `static` modifier, which causes multiple broker instances to share the same thread pool. ### Describe the Solution You'd Like Each broker instance should have its own independent transaction message checking thread pool to ensure resource isolation and correct task execution. ### Describe Alternatives You've Considered No ### Additional Context No -- 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]
