[Enhancement] Fix static executorService in AbstractTransactionalMessageCheckListener for multi-broker support #9771
Description
Before Creating the Enhancement Request
- 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