ThreadPoolStatusChecker get wrong pool size message

[YoungHu]

• [x] I have searched the issues of this repository and believe that this is not a duplicate.
• [x] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

• Dubbo version: 2.6.x
• Operating System version: all
• Java version: all

Steps to reproduce this issue

1. set dubbo thread pool to be 100 <dubbo:protocol port="-1" dispatcher="all" threadpool="fixed" threads="100"/> and enable dubbo monitor <dubbo:monitor protocol="registry" interval="10000"/>

2. start dubbo provider application

3. run telnet localhost 20880 when show dubbo flag then run status -l will get pool size is 100

4. start a dubbo consumer applicaiton

5. do step 3 again, pool size change to 0

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

step 5 should show pool size is 100

Actual Result

step 5 show pool size is 0

Troubleshooting

Then the executor changed to MonitorService executor with no pool.

solution

best:

add map.put(Constants.SIDE_KEY, Constants.CONSUMER_SIDE); into AbstractInterfaceConfig.loadMonitor method

temporary fix:

dubbo monitor config like this

[chickenlj]

I am a bit confused here. Most of the time status -l should be used to monitor the status of the Dubbo provider threadpool. What's the meaning of showing the pool of the Consumer consuming MonitorService?

[YoungHu]

yes, status -l is use to monitor the status of the dubbo provider thread pool. but dubbo monitor haven't mark it self as consumer, so it override the provider thread pool data. finally, we got the wrong data.