Skip to content
New issue

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

Dubbo-thread-xxx threads that should not appear on the consumer side #6887

Closed
2 tasks done
tongxiao0622 opened this issue Nov 8, 2020 · 1 comment
Closed
2 tasks done
Labels
help wanted Everything needs help from contributors type/bug Bugs to being fixed

Comments

@tongxiao0622
Copy link

tongxiao0622 commented Nov 8, 2020

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

Environment

  • Dubbo version: 2.7.8
  • Operating System version: mac os
  • Java version: 1.8

Steps to reproduce this issue

  1. Start multiple provider nodes
    (中文:启动多个提供方节点)

  2. Start consumer node
    (中文:启动消费方节点)

  3. Frequently shutdown and restart provider nodes or Frequently enable and disable provider nodes
    (中文:频繁关闭、重启提供方节点或者频繁启用、禁用提供方节点)

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

Expected Result

What do you expected from the above steps?

Only the thread of DubboClientHandler-xxx will appear
(中文:应该只会出现DubboClientHandler-xxx的线程用于网络连接、断连,因为获取响应结果用的是主线程)

Actual Result

What actually happens?

There are many threads named with Dubbo-thread-xxx on the consumer side,these threads will not be recycled.
(中文:消费方出现了很多以Dubbo-thread-xxx命名的线程,这些线程不会被回收)

@CrazyHZM
Copy link
Member

CrazyHZM commented Nov 3, 2021

Resolved in #7109

@CrazyHZM CrazyHZM closed this as completed Nov 3, 2021
@CrazyHZM CrazyHZM removed this from the 3.0.5 milestone Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Everything needs help from contributors type/bug Bugs to being fixed
Projects
None yet
Development

No branches or pull requests

2 participants