<h3 dir="auto">Dubbo Version: 2.5.3</h3>
<p dir="auto">I have a large provider cluster with more than 30 instances. And I found that in client side, the consumer uses a stand alone thread pools for each instances, so there are 30 thread pool to consume the service, which I can find out from the jstack that I have many diffrent thread groups named like DubboClientHandler-IP1-XXX.</p>
<p dir="auto">Question1:<br>
I guess the consumer uses stand alone cached thread pool for each provider instances but with the max pool size of "default.actives", am I right?</p>
<p dir="auto">Question2:<br>
But the problem is that, I hope to maximize the tps , so I provide a very large cluster, but now the consumer will suffer from high cpu consumption due to large thread counts.</p>
<p dir="auto">Can I change the thread model in consumer side? Like I use a shared thread pool so that I can control the maximum thread size.</p>
<hr>
<p dir="auto">我有一个非常大的provider 集群（30个实例）。然后我们发现在客户端，为每一个实例，都准备了一个独立线程池，所以我们看到有30个线程池以去发起消费请求，这个从jstack堆栈上可以证明，因为里面很多线程组的名字是类似DubboClientHandler-IP1-XXX，其中ip都是不一样的。</p>
<p dir="auto">问题1：</p>
<p dir="auto">按照我的猜测，每个实例是应该会有一个cached的线程池（可回收），然后其中的最大线程数是default.actives，是否如此？</p>
<p dir="auto">问题2：</p>
<p dir="auto">之所以我们提供如此大的服务集群，是因为我们希望最大化TPS，但现在集群是大了，但是消费者又因此导致巨大的线程消耗（高CPU）。我们能否通过配置改变这个线程的模型，例如用一个共享的线程池去处理所有的服务实例，这样最大的线程数便可控了。</p>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have searched the <a href="https://github.com/apache/incubator-dubbo/issues">issues</a> of this repository and believe that this is not a duplicate.</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have checked the <a href="https://github.com/apache/incubator-dubbo/blob/master/FAQ.md">FAQ</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<h3 dir="auto">Environment</h3>
<ul dir="auto">
<li>Dubbo version: 2.6.5</li>
<li>Operating System version: win10</li>
<li>Java version: 1.8</li>
</ul>
<h3 dir="auto">Steps to reproduce this issue</h3>
<p dir="auto">使用dubbo-spring-boot-starter,之前是用 dubbo-spring-boot-starter 自动引入的 2.6.2,没问题(除了QOS端口修改不生效),后面听说 2.6.5解决了QOS端口修改不了的问题.<br>
然后通过单独修改 dubbo 版本号的方式升级到了 2.6.5,其他什么都没动.启动项目后报错: com.alibaba.spring.util.PropertySourcesUtils  找不到.<br>
对比了报错部分的源码, 2.6.2 使用的是  com.alibaba.dubbo.config.spring.util.PropertySourcesUtils,该类就在dubbo的jar包里<br>
而 2.6.5 用的是 com.alibaba.spring.util.PropertySourcesUtils<br>
实在找不到 2.6.5 使用的 PropertySourcesUtils  在哪个包......</p>