Who is Using Dubbo

First of all, thanks sincerely for constantly using and supporting dubbo. We will try our best to keep dubbo better, and keep growing community and eco-system.

The purpose of this issue

• We’d like to listen to the community to make dubbo better.
• We want to attract more people to contribute to dubbo.
• We're willing to learn more dubbo use scenarios in the field for better planning.

What we expect from you

Pls. submit a comment in this issue to include the following infomation:

• your company, school or organization.
• your city and country.
• your contact info: blog, email, twitter (at least one).
• for what business scenario do you use dubbo

You can refer to the following sample answer for the format:

* Orgnizatioin: Alibaba
* Location: Hangzhou, China
* Contact: [email protected]
* Purpose: used as cornerstone in distributed service architecture alibaba switched years ago.

Thanks again for your participation ! Dubbo Team

谁在使用 Dubbo

首先诚挚地感谢每一位持续关注并使用 Dubbo 的朋友。我们会持续投入，力图把 dubbo 变得更好，把 dubbo 社区和生态变得更加繁荣。

此 Issue 的目的

• 聆听社区的声音，让 dubbo 变得更好
• 吸引更多的人参与贡献
• 更多的了解 dubbo 的实际使用场景，以方便下一步的规划

我们期待您能提供

在此提交一条评论, 评论内容包括:

• 您所在公司、学校或组织
• 您所在的城市、国家
• 您的联系方式: 微博、邮箱、微信 (至少一个)
• 您将 dubbo 用于哪些业务场景

您可以参考下面的样例来提供您的信息：

* 组织：阿里巴巴
* 地点：中国杭州
* 联系方式：[email protected]
* 场景：阿里内部服务化改造

再次感谢你的参与!!! Dubbo 团队

A调用服务B，超时时间1秒，从某些请求来看超时了两次，重试了两次，第三次成功了，耗时仅4ms。

客户端有类似日志：

2018-05-11 00:00:14.741 [T_Common_DispatchExecutor_43] WARN  com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker -  [DUBBO] Although retry the method push in the service com.oppo.push.open.basic.api.service.BroadcastService was successful by the provider 10.12.
26.124:9000, but there have been failed providers [10.12.26.137:9000] (1/6) from the registry 10.12.26.154:2181 on the consumer 10.12.26.102 using the dubbo version 2.5.3. Last error is: Invoke remote method timeout. method: push, provider: dubbo://10.12.26.137:9000/com
.oppo.push.open.basic.api.service.BroadcastService?accesslog=false&anyhost=true&application=push-open-platform-gateway-server&check=false&default.delay=-1&default.service.filter=-exception&default.timeout=1000&delay=-1&dubbo=2.5.3&interface=com.oppo.push.open.basic.api.
service.BroadcastService&loadbalance=random&logger=slf4j&methods=revokePushMessage,revokeSmsMessage,push&pid=31597&push.retries=2&revision=3.0.2-SNAPSHOT&side=consumer&timestamp=1525937532890&transporter=netty, cause: Waiting server-side response timeout by scan timer. 
start time: 2018-05-11 00:00:13.710, end time: 2018-05-11 00:00:14.738, client elapsed: 0 ms, server elapsed: 1028 ms, timeout: 1000 ms, request: Request [id=2395465, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=push, parameterTy
pes=[class com.oppo.push.open.basic.api.domain.PushTask], arguments=[PushTask[taskId=5af46c8da609e97b6dc17380, messageId=5af4655dad99497f2345ccda, messageCategory=3, messageType=1, taskStatus=5, target=PushTarget{id='5af46c8da609e97b6dc17381', type=REGISTRATION_ID, valu
e='6187cd138ad2dbceee7f044c2409d4f1;ab5721987d21dcf5e863b58e165f144a;827f4ff3b5d31cce9e441b045eb985c9;e17854797bb4f0e7b14178cbde596c88;CN_647982d13860dde6876cdf0e37165c76;93624a57d555510bcf27cda47d5a06f9;eb3ebc3a53b12ef304de95b3e1852c60;5b752dc47cbca9721239885a062814c2;
c69bd502aee453f0b78517bc9cb4548d;cc35de8b5edbff28dbaf55e4f60ad20a;CN_1239d29db4f5db54cc1bef51df3f3acc;CN_f6fd0448d1c6281da6ffa50df4d26f38;CN_2c2dc12e3c567ad81a00ca9cdca564e3;CN_d92b53c07de3e70883552295ece900f1;CN_b1cedf2537fd52e91fa29b5fb3c4eb47;525fb9de1d18e21c15479a0a
7f59b163;CN_debc0d6366f27dea1a45862020687f1a;d5bbb9bae7102ad0d69b3aeb138c4ff4;aac05d1a20d073343917c68798f9be2f;817898207275b2dbeefb6e9398f06b50;203e1b8c0de742605ecb166b6a92d9ce;8c6a4f0925ba3a1d92e3640d00507ade;fc3e47ab8ca527d964fae84ab5db00d7;d9c2ecf8051093bf7eb7818bbe5
5ec8f;c7894071806e5a6540a5380b1763e91b;b56b7a3e247258034876b9a8522b0dab;8b17b0c449bffa08407a4401f33b988f;789ca011db0844d01932fb8da2553a03;735e6aae28a3f2d5752e65f277bea9c3;e2cfca07e576a0285ab8f50dbaa3a947;8428d377795b069d9dfe033e880ed627;0939eab473c0311b5dd5567f5d191487;
ec2ff892fbc28fdf0008d532a2c48560;e3df5c83de7f985e73d4e58d4d15225d;CN_c5af7007e71c23771b29eb0713cde7e2;ef91ece8b7e44a13fb31015f8f20b25b;CN_57b78f69e35ce1f8c1fcb27e36758fca;CN_d58cb83cdd32f108f84ff6eae662712f;CN_5564f22ea67f3391fc0f37b23d68ade0;e2b842e3aea81c7e7784fae318e
bfb8a;2315554dca29eac7100d823f262c2b6f;18c0676bc2300630bad171d72353de0b;116c0728d4d8bed6aa80ba78a77620c1;11c37c408a7c88cf80e7bca695228c05;643413c1adad5e72df94594017797078;CN_c8dedeeeacdc24e9194386929e5367a7;CN_77a3fc33b094c592bad79d1aa95761af;4b9ceaaac2fbca88c01c3976c4a
c7849;0a1c506ef41acca7bf4c01a758ece6cb;66c0c30821c399e06bb63cfd630b2016;2a5efb3ee633035f5d3700dc744b97d2;07348c108d514773761a828499877ce4;4532d9d99307e6b3634fdfc06aecbb09;6aae440b59761d2ed4e425206f276dc7', effectiveValue='null', unsubscribeValue='null', deviceId='null'}
, appId=nJNKY574F2C4TWrAqYobsa3X, creator=null, messageTitle=null, createTime=Fri May 11 00:00:13 CST 2018, updateTime=Fri May 11 00:00:13 CST 2018], finishTime=null], extFields={}]], attachments={path=com.oppo.push.open.basic.api.service.BroadcastService, interface=com
.oppo.push.open.basic.api.service.BroadcastService, timeout=1000, version=0.0.0}]], channel: /10.12.26.102:49081 -> /10.12.26.137:9000, dubbo version: 2.5.3, current host: 10.12.26.102
com.alibaba.dubbo.rpc.RpcException: Invoke remote method timeout. method: push, provider: dubbo://10.12.26.137:9000/com.oppo.push.open.basic.api.service.BroadcastService?accesslog=false&anyhost=true&application=push-open-platform-gateway-server&check=false&default.delay
=-1&default.service.filter=-exception&default.timeout=1000&delay=-1&dubbo=2.5.3&interface=com.oppo.push.open.basic.api.service.BroadcastService&loadbalance=random&logger=slf4j&methods=revokePushMessage,revokeSmsMessage,push&pid=31597&push.retries=2&revision=3.0.2-SNAPSH
OT&side=consumer&timestamp=1525937532890&transporter=netty, cause: Waiting server-side response timeout by scan timer. start time: 2018-05-11 00:00:13.710, end time: 2018-05-11 00:00:14.738, client elapsed: 0 ms, server elapsed: 1028 ms, timeout: 1000 ms, request: Reque
st [id=2395465, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=push, parameterTypes=[class com.oppo.push.open.basic.api.domain.PushTask], arguments=[PushTask[taskId=5af46c8da609e97b6dc17380, messageId=5af4655dad99497f2345ccda, mess
ageCategory=3, messageType=1, taskStatus=5, target=PushTarget{id='5af46c8da609e97b6dc17381', type=REGISTRATION_ID, value='6187cd138ad2dbceee7f044c2409d4f1;ab5721987d21dcf5e863b58e165f144a;827f4ff3b5d31cce9e441b045eb985c9;e17854797bb4f0e7b14178cbde596c88;CN_647982d13860d
de6876cdf0e37165c76;93624a57d555510bcf27cda47d5a06f9;eb3ebc3a53b12ef304de95b3e1852c60;5b752dc47cbca9721239885a062814c2;c69bd502aee453f0b78517bc9cb4548d;cc35de8b5edbff28dbaf55e4f60ad20a;CN_1239d29db4f5db54cc1bef51df3f3acc;CN_f6fd0448d1c6281da6ffa50df4d26f38;CN_2c2dc12e3c
567ad81a00ca9cdca564e3;CN_d92b53c07de3e70883552295ece900f1;CN_b1cedf2537fd52e91fa29b5fb3c4eb47;525fb9de1d18e21c15479a0a7f59b163;CN_debc0d6366f27dea1a45862020687f1a;d5bbb9bae7102ad0d69b3aeb138c4ff4;aac05d1a20d073343917c68798f9be2f;817898207275b2dbeefb6e9398f06b50;203e1b8
c0de742605ecb166b6a92d9ce;8c6a4f0925ba3a1d92e3640d00507ade;fc3e47ab8ca527d964fae84ab5db00d7;d9c2ecf8051093bf7eb7818bbe55ec8f;c7894071806e5a6540a5380b1763e91b;b56b7a3e247258034876b9a8522b0dab;8b17b0c449bffa08407a4401f33b988f;789ca011db0844d01932fb8da2553a03;735e6aae28a3f
2d5752e65f277bea9c3;e2cfca07e576a0285ab8f50dbaa3a947;8428d377795b069d9dfe033e880ed627;0939eab473c0311b5dd5567f5d191487;ec2ff892fbc28fdf0008d532a2c48560;e3df5c83de7f985e73d4e58d4d15225d;CN_c5af7007e71c23771b29eb0713cde7e2;ef91ece8b7e44a13fb31015f8f20b25b;CN_57b78f69e35ce
1f8c1fcb27e36758fca;CN_d58cb83cdd32f108f84ff6eae662712f;CN_5564f22ea67f3391fc0f37b23d68ade0;e2b842e3aea81c7e7784fae318ebfb8a;2315554dca29eac7100d823f262c2b6f;18c0676bc2300630bad171d72353de0b;116c0728d4d8bed6aa80ba78a77620c1;11c37c408a7c88cf80e7bca695228c05;643413c1adad5
e72df94594017797078;CN_c8dedeeeacdc24e9194386929e5367a7;CN_77a3fc33b094c592bad79d1aa95761af;4b9ceaaac2fbca88c01c3976c4ac7849;0a1c506ef41acca7bf4c01a758ece6cb;66c0c30821c399e06bb63cfd630b2016;2a5efb3ee633035f5d3700dc744b97d2;07348c108d514773761a828499877ce4;4532d9d99307e
6b3634fdfc06aecbb09;6aae440b59761d2ed4e425206f276dc7', effectiveValue='null', unsubscribeValue='null', deviceId='null'}, appId=nJNKY574F2C4TWrAqYobsa3X, creator=null, messageTitle=null, createTime=Fri May 11 00:00:13 CST 2018, updateTime=Fri May 11 00:00:13 CST 2018], f
inishTime=null], extFields={}]], attachments={path=com.oppo.push.open.basic.api.service.BroadcastService, interface=com.oppo.push.open.basic.api.service.BroadcastService, timeout=1000, version=0.0.0}]], channel: /10.12.26.102:49081 -> /10.12.26.137:9000
        at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:99)
        at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144)
        at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74)
        at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53)
        at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)
        at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75)
        at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)
        at com.oppo.trace.dubbo.DubboConsumerTraceFilter.invoke(DubboConsumerTraceFilter.java:37)
        at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)
        at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48)
        at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)
        at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53)
        at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77)
        at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227)
        at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72)
        at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52)
        at com.alibaba.dubbo.common.bytecode.proxy0.push(proxy0.java)
        at com.oppo.push.open.platform.gateway.action.notification.NotificationBroadcastAction.doExecute(NotificationBroadcastAction.java:105)
        at com.oppo.push.open.platform.gateway.action.AbstractAction.execute(AbstractAction.java:51)
        at com.oppo.push.httpframework.Action.ActionCallable$1.exec(ActionCallable.java:39)
        at com.oppo.push.httpframework.Action.ActionCallable$1.exec(ActionCallable.java:36)
        at com.oppo.push.httpframework.common.TraceTemplate.rootExec(TraceTemplate.java:24)
        at com.oppo.push.httpframework.Action.ActionCallable.run(ActionCallable.java:36)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2018-05-11 00:00:13.710, end time: 2018-05-11 00:00:14.738, client elapsed: 0 ms, server elapsed: 1028 ms, timeout: 1000 ms, request: Request [id=2395
465, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=push, parameterTypes=[class com.oppo.push.open.basic.api.domain.PushTask], arguments=[PushTask[taskId=5af46c8da609e97b6dc17380, messageId=5af4655dad99497f2345ccda, messageCategory
=3, messageType=1, taskStatus=5, target=PushTarget{id='5af46c8da609e97b6dc17381', type=REGISTRATION_ID, value='6187cd138ad2dbceee7f044c2409d4f1;ab5721987d21dcf5e863b58e165f144a;827f4ff3b5d31cce9e441b045eb985c9;e17854797bb4f0e7b14178cbde596c88;CN_647982d13860dde6876cdf0e
37165c76;93624a57d555510bcf27cda47d5a06f9;eb3ebc3a53b12ef304de95b3e1852c60;5b752dc47cbca9721239885a062814c2;c69bd502aee453f0b78517bc9cb4548d;cc35de8b5edbff28dbaf55e4f60ad20a;CN_1239d29db4f5db54cc1bef51df3f3acc;CN_f6fd0448d1c6281da6ffa50df4d26f38;CN_2c2dc12e3c567ad81a00c
a9cdca564e3;CN_d92b53c07de3e70883552295ece900f1;CN_b1cedf2537fd52e91fa29b5fb3c4eb47;525fb9de1d18e21c15479a0a7f59b163;CN_debc0d6366f27dea1a45862020687f1a;d5bbb9bae7102ad0d69b3aeb138c4ff4;aac05d1a20d073343917c68798f9be2f;817898207275b2dbeefb6e9398f06b50;203e1b8c0de742605e
cb166b6a92d9ce;8c6a4f0925ba3a1d92e3640d00507ade;fc3e47ab8ca527d964fae84ab5db00d7;d9c2ecf8051093bf7eb7818bbe55ec8f;c7894071806e5a6540a5380b1763e91b;b56b7a3e247258034876b9a8522b0dab;8b17b0c449bffa08407a4401f33b988f;789ca011db0844d01932fb8da2553a03;735e6aae28a3f2d5752e65f2
77bea9c3;e2cfca07e576a0285ab8f50dbaa3a947;8428d377795b069d9dfe033e880ed627;0939eab473c0311b5dd5567f5d191487;ec2ff892fbc28fdf0008d532a2c48560;e3df5c83de7f985e73d4e58d4d15225d;CN_c5af7007e71c23771b29eb0713cde7e2;ef91ece8b7e44a13fb31015f8f20b25b;CN_57b78f69e35ce1f8c1fcb27e
36758fca;CN_d58cb83cdd32f108f84ff6eae662712f;CN_5564f22ea67f3391fc0f37b23d68ade0;e2b842e3aea81c7e7784fae318ebfb8a;2315554dca29eac7100d823f262c2b6f;18c0676bc2300630bad171d72353de0b;116c0728d4d8bed6aa80ba78a77620c1;11c37c408a7c88cf80e7bca695228c05;643413c1adad5e72df945940
17797078;CN_c8dedeeeacdc24e9194386929e5367a7;CN_77a3fc33b094c592bad79d1aa95761af;4b9ceaaac2fbca88c01c3976c4ac7849;0a1c506ef41acca7bf4c01a758ece6cb;66c0c30821c399e06bb63cfd630b2016;2a5efb3ee633035f5d3700dc744b97d2;07348c108d514773761a828499877ce4;4532d9d99307e6b3634fdfc0
6aecbb09;6aae440b59761d2ed4e425206f276dc7', effectiveValue='null', unsubscribeValue='null', deviceId='null'}, appId=nJNKY574F2C4TWrAqYobsa3X, creator=null, messageTitle=null, createTime=Fri May 11 00:00:13 CST 2018, updateTime=Fri May 11 00:00:13 CST 2018], finishTime=n
ull], extFields={}]], attachments={path=com.oppo.push.open.basic.api.service.BroadcastService, interface=com.oppo.push.open.basic.api.service.BroadcastService, timeout=1000, version=0.0.0}]], channel: /10.12.26.102:49081 -> /10.12.26.137:9000
        at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.returnFromResponse(DefaultFuture.java:188)
        at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:110)
        at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84)
        at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96)
        ... 27 common frames omitted

有以下两个奇怪的地方：

1. 从报超时的服务端上看，找不到对应的超时的warn日志
2. 从我们内部服务端统计的耗时来看，此接口从来没有大于100ms的。

以下是我的分析：

猜测和dubbo 服务端进入业务线程前的排队有关，但是我们没有设置queue的长度，所以默认应该是不排队的，线程池耗尽应该抛出的异常不是timeout。

即使排队了，但是服务端没有找到此上下文的超时日志，感觉像完全没有收到此请求？

会不会是直接网络上丢了包？如果网络上传输就失败了，异常会是超时么？此请求是一个对象，转换为JSON后有几K。

求解答

ERROR context.ContextLoader - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'uriBrokerService': Cannot create inner bean '(inner bean)' of type [com.alibaba.citrus.service.uribroker.impl.URIBrokerServiceImpl$URIBrokerInfo] while setting bean property 'brokers' with key [0]; nested excepti
on is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#25': Cannot create inner bean 'server' of type [com.alibaba.citrus.service.uribroker.uri.GenericURIBroker] while setting constructor argument; nested exception is org.springframework.beans.fact
ory.BeanCreationException: Error creating bean with name 'server': Error setting property values; nested exception is org.springframework.beans.NotWritablePropertyException: Invalid property 'URIType' of bean class [com.alibaba.citrus.service.uribroker.uri.GenericURIBroker]: Bean property 'URIType'
is not writable or has an invalid setter method. Does the parameter type of the setter match the return type of the getter?
        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:230)
        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:122)
        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:287)

Environment

• Dubbo version: 2.7.8
• Operating System version:win10
• Java version: 1.8

information

服务重复注册，用的是dububo:2.7.8, spring-boot:2.3.0.RELEASE，我的pom

   <dependency>
             <groupId>org.apache.dubbo</groupId>
             <artifactId>dubbo-spring-boot-starter</artifactId>
             <version>${dubbo.version}</version>
         </dependency>
         <dependency>
             <groupId>org.apache.dubbo</groupId>
             <artifactId>dubbo-dependencies-zookeeper</artifactId>
             <version>${dubbo.version}</version>
             <type>pom</type>
             <exclusions>
                 <exclusion>
                     <groupId>org.slf4j</groupId>
                     <artifactId>slf4j-log4j12</artifactId>
                 </exclusion>
             </exclusions>
         </dependency>

dubbo服务

@DubboService(version = "1.0.0", validation = "true", dynamic = true)
public class AccountRemoteServiceImpl implements AccountRemoteService {
    @Autowired
    AccountBizService accountBizService;

    @Override
    public Boolean debit(String userId, BigDecimal money) {
        return  accountBizService.debit(userId, money);
    }
}

查看zk服务的节点信息，

ip地址一样；

从4213来看，同样存在这样的问题？说是dynamic的问题，默认false，则持久路径，true为临时路径，2.7.8为true还是没用。 DubboService ···java /** * Whether the service is dynamic, default value is true */ boolean dynamic() default true; ···

调试结果：

临时节点，在连接断开后，zk会自动删除， 这不应该呀！

我们dubbo版本为2.6.9,dubbo-boot：0.2.1.RELEASE，spring-boot:2.1..RELEASE 存在同样的问题，重复注册？ pom

<!--0.2.1.RELEASE start-->
        <dependency>
            <groupId>com.alibaba.boot</groupId>
            <artifactId>dubbo-spring-boot-starter</artifactId>
            <version>${alibaba.boot.dubbo.springboot.starter}</version>
        </dependency>
        <dependency>
            <groupId>com.alibaba</groupId>
            <artifactId>dubbo</artifactId>
            <version>${dubbo.version}</version>
        </dependency>
        <dependency>
            <groupId>org.apache.curator</groupId>
            <artifactId>curator-framework</artifactId>
            <version>2.8.0</version>
            <exclusions>
                <exclusion>
                    <groupId>com.google.guava</groupId>
                    <artifactId>guava</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>org.apache.curator</groupId>
            <artifactId>curator-recipes</artifactId>
            <version>2.8.0</version>
        </dependency>
        <dependency>
            <groupId>io.netty</groupId>
            <artifactId>netty-all</artifactId>
            <version>4.1.15.Final</version>
        </dependency>
        <!--0.2.1.RELEASE end-->

dubbo 服务

@Service(version = "1.0.0", validation = "true", dynamic = true)
public class AccountRemoteServiceImpl implements AccountRemoteService {
    @Autowired
    AccountBizService accountBizService;

    @Override
    public Boolean debit(String userId, BigDecimal money) {
        return  accountBizService.debit(userId, money);
    }
}

然而注解service为false

public @interface Service {
...
 boolean dynamic() default false;
...
}

dynamic 为false还是有；

从这两个例子来看，跟dynamic 无关。

这是一个问题，另外我想问一下，服务节点路径的timestamp 是做什么用了

/dubbo/com.story.home.cherry.api.domain.account.service.AccountRemoteService/providers/dubbo%3A%2F%2F10.242.214.156%3A20880%2Fcom.story.home.cherry.api.domain.account.service.AccountRemoteService%3Fanyhost%3Dtrue%26application%3Dcomosus-cherry%26deprecated%3Dfalse%26dubbo%3D2.0.2%26dynamic%3Dtrue%26generic%3Dfalse%26interface%3Dcom.story.home.cherry.api.domain.account.service.AccountRemoteService%26metadata-type%3Dremote%26methods%3Ddebit%26pid%3D14688%26release%3D2.7.8%26retries%3D0%26revision%3D1.0.0%26service.filter%3DelapsedTimeFilter%26side%3Dprovider%26threads%3D400%26timeout%3D6000000%26timestamp%3D1611295886073%26version%3D1.0.0

去掉timestamp，是不是，就保持一个节点了, 但这不是根本问题。

• [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.2 Operating System version: win7 Java version: 1.8

Step to reproduce this issue

阅读源码发现，每个代理实现类都会去判断默认实现

public class Protocol$Adaptive implements org.apache.dubbo.rpc.Protocol
{
    public void destroy()
    {
        throw new UnsupportedOperationException(
                "method public abstract void org.apache.dubbo.rpc.Protocol.destroy() of interface org.apache.dubbo.rpc.Protocol is not adaptive method!");
    }

    public int getDefaultPort()
    {
        throw new UnsupportedOperationException(
                "method public abstract int org.apache.dubbo.rpc.Protocol.getDefaultPort() of interface org.apache.dubbo.rpc.Protocol is not adaptive method!");
    }

    public org.apache.dubbo.rpc.Invoker refer(java.lang.Class arg0, org.apache.dubbo.common.URL arg1)
        throws org.apache.dubbo.rpc.RpcException
    {
        if (arg1 == null)
            throw new IllegalArgumentException("url == null");
        org.apache.dubbo.common.URL url = arg1;
        String extName = (url.getProtocol() == null ? "dubbo" : url.getProtocol());
        if (extName == null)
            throw new IllegalStateException("Fail to get extension(org.apache.dubbo.rpc.Protocol) name from url("
                    + url.toString() + ") use keys([protocol])");
        org.apache.dubbo.rpc.Protocol extension = (org.apache.dubbo.rpc.Protocol) ExtensionLoader
                .getExtensionLoader(org.apache.dubbo.rpc.Protocol.class).getExtension(extName);
        return extension.refer(arg0, arg1);
    }

    public org.apache.dubbo.rpc.Exporter export(org.apache.dubbo.rpc.Invoker arg0)
        throws org.apache.dubbo.rpc.RpcException
    {
        if (arg0 == null)
            throw new IllegalArgumentException("org.apache.dubbo.rpc.Invoker argument == null");
        if (arg0.getUrl() == null)
            throw new IllegalArgumentException("org.apache.dubbo.rpc.Invoker argument getUrl() == null");
        org.apache.dubbo.common.URL url = arg0.getUrl();
        String extName = (url.getProtocol() == null ? "dubbo" : url.getProtocol());
        if (extName == null)
            throw new IllegalStateException("Fail to get extension(org.apache.dubbo.rpc.Protocol) name from url("
                    + url.toString() + ") use keys([protocol])");
        org.apache.dubbo.rpc.Protocol extension = (org.apache.dubbo.rpc.Protocol) ExtensionLoader
                .getExtensionLoader(org.apache.dubbo.rpc.Protocol.class).getExtension(extName);
        return extension.export(arg0);
    }
}

Environment

• Dubbo version: 3.0

Steps to reproduce this issue

现在dubbo3.0在github构建动不动就timeout，看了一下workflow的build-and-test-3.yml，unit test的timeout-minutes分别是40分钟(with Integration Tests)和50分钟(without Integration Tests)，干脆都改成60分钟，效果好多了，但是还是有构建失败，查了日志发现充斥着这个东西： [Curator-ConnectionStateManager-0] WARN org.apache.curator.framework.state.ConnectionStateManager - Session timeout has elapsed while SUSPENDED. Injecting a session expiration. Elapsed ms: 63515. Adjusted session timeout ms: 60000 确认了一下这个是个缺陷，4.1.0才修复，而dubbo使用的版本是4.0.1 https://issues.apache.org/jira/browse/CURATOR-405

• Dubbo version: 3.0

实测发现GlobalResourcesRepository对github的单元测试和集成测试均有影响。

首先说一下github集成测试时，如下所示，当启动一个测试类时，却开始去执行前面一个测试类的全局资源释放操作，导致正在启动的测试类各种异常：

2021-10-20T13:28:53.6306484Z Running org.apache.dubbo.samples.version.VersionServiceStarIT 
<== 开始测试VersionServiceStarIT 
2021-10-20T13:28:53.6317495Z [20/10/21 01:28:12:012 UTC] main  INFO support.DefaultTestContextBootstrapper: Loaded default TestExecutionListener class names from location [META-INF/spring.factories]: 
<== 加载TestExecutionListener （这个新增的TestExecutionListener 也会导致用全局资源的测试类出现问题，另开了issue）
...
2021-10-20T13:28:53.6419566Z [20/10/21 01:28:12:012 UTC] main  INFO deploy.DefaultApplicationDeployer:  [DUBBO] Dubbo application[1.1] is stopping., dubbo version: 3.0.4-SNAPSHOT, current host: 192.168.160.5
<==  application[1.1] 是前面已经完成测试的VersionService1IT创建的，现在才开始销毁了

2021-10-20T13:28:53.6558073Z [20/10/21 01:28:12:012 UTC] main  INFO model.FrameworkModel:  [DUBBO] Dubbo framework[1] is destroying ..., dubbo version: 3.0.4-SNAPSHOT, current host: 192.168.160.5
<== 开始销毁VersionService1IT的framework model

2021-10-20T13:28:53.6559810Z [20/10/21 01:28:12:012 UTC] main  INFO dubbo.DubboProtocol:  [DUBBO] Destroying protocol [DubboProtocol] ..., dubbo version: 3.0.4-SNAPSHOT, current host: 192.168.160.5
2021-10-20T13:28:53.6577037Z [20/10/21 01:28:12:012 UTC] main  INFO model.FrameworkModel:  [DUBBO] Dubbo framework[1] is destroyed, dubbo version: 3.0.4-SNAPSHOT, current host: 192.168.160.5
2021-10-20T13:28:53.6578732Z [20/10/21 01:28:12:012 UTC] main  INFO resource.GlobalResourcesRepository:  [DUBBO] Destroying global resources ..., dubbo version: 3.0.4-SNAPSHOT, current host: 192.168.160.5
2021-10-20T13:28:53.6580622Z [20/10/21 01:28:12:012 UTC] main  INFO resource.GlobalResourcesRepository:  [DUBBO] Dubbo is completely destroyed, dubbo version: 3.0.4-SNAPSHOT, current host: 192.168.160.5
<== 销毁完毕

<== 然后开始测试就直接抛DubboProtocol is destroyed异常
2021-10-20T13:28:53.6694315Z [20/10/21 01:28:13:013 UTC] main ERROR integration.RegistryDirectory:  [DUBBO] Failed to refer invoker for interface:interface org.apache.dubbo.samples.version.api.VersionService,url:(dubbo://192.168.160.3:20880/org.apache.dubbo.samples.version.api.VersionService?anyhost=true&application=version-provider&background=false&check=false&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&interface=org.apache.dubbo.samples.version.api.VersionService&metadata-type=remote&methods=sayHello&release=3.0.4-SNAPSHOT&revision=1.0.0&service-name-mapping=true&side=provider&token=1de93a01-b8f8-4f81-aa28-653b638e83ed&version=1.0.0)DubboProtocol is destroyed, dubbo version: 3.0.4-SNAPSHOT, current host: 192.168.160.5
2021-10-20T13:28:53.6699094Z java.lang.IllegalStateException: DubboProtocol is destroyed
2021-10-20T13:28:53.6700889Z 	at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.checkDestroyed(DubboProtocol.java:346)
2021-10-20T13:28:53.6703229Z 	at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.refer(DubboProtocol.java:421)
2021-10-20T13:28:53.6705268Z 	at org.apache.dubbo.qos.protocol.QosProtocolWrapper.refer(QosProtocolWrapper.java:85)
2021-10-20T13:28:53.6707565Z 	at org.apache.dubbo.rpc.protocol.ProtocolListenerWrapper.refer(ProtocolListenerWrapper.java:77)
2021-10-20T13:28:53.6710150Z 	at org.apache.dubbo.rpc.cluster.filter.ProtocolFilterWrapper.refer(ProtocolFilterWrapper.java:74)
2021-10-20T13:28:53.6712930Z 	at org.apache.dubbo.rpc.protocol.ProtocolSerializationWrapper.refer(ProtocolSerializationWrapper.java:52)
2021-10-20T13:28:53.6714976Z 	at org.apache.dubbo.rpc.Protocol$Adaptive.refer(Protocol$Adaptive.java)
2021-10-20T13:28:53.6716909Z 	at org.apache.dubbo.registry.integration.RegistryDirectory.toInvokers(RegistryDirectory.java:376)
2021-10-20T13:28:53.6719727Z 	at org.apache.dubbo.registry.integration.RegistryDirectory.refreshInvoker(RegistryDirectory.java:235)
2021-10-20T13:28:53.6723032Z 	at org.apache.dubbo.registry.integration.RegistryDirectory.refreshOverrideAndInvoker(RegistryDirectory.java:187)
2021-10-20T13:28:53.6726085Z 	at org.apache.dubbo.registry.integration.RegistryDirectory.notify(RegistryDirectory.java:164)
2021-10-20T13:28:53.6728400Z 	at org.apache.dubbo.registry.support.AbstractRegistry.notify(AbstractRegistry.java:439)
2021-10-20T13:28:53.6730626Z 	at org.apache.dubbo.registry.support.FailbackRegistry.doNotify(FailbackRegistry.java:371)
2021-10-20T13:28:53.6732859Z 	at org.apache.dubbo.registry.support.FailbackRegistry.notify(FailbackRegistry.java:363)
2021-10-20T13:28:53.6816166Z 	at org.apache.dubbo.registry.zookeeper.ZookeeperRegistry.doSubscribe(ZookeeperRegistry.java:190)
2021-10-20T13:28:53.6818703Z 	at org.apache.dubbo.registry.support.FailbackRegistry.subscribe(FailbackRegistry.java:298)
2021-10-20T13:28:53.6821130Z 	at org.apache.dubbo.registry.ListenerRegistryWrapper.subscribe(ListenerRegistryWrapper.java:109)
2021-10-20T13:28:53.6823746Z 	at org.apache.dubbo.registry.integration.RegistryDirectory.subscribe(RegistryDirectory.java:119)
2021-10-20T13:28:53.6826502Z 	at org.apache.dubbo.registry.integration.RegistryProtocol.doCreateInvoker(RegistryProtocol.java:560)
2021-10-20T13:28:53.6830203Z 	at org.apache.dubbo.registry.integration.InterfaceCompatibleRegistryProtocol.getInvoker(InterfaceCompatibleRegistryProtocol.java:58)
2021-10-20T13:28:53.6834332Z 	at org.apache.dubbo.registry.client.migration.MigrationInvoker.refreshInterfaceInvoker(MigrationInvoker.java:448)
2021-10-20T13:28:53.6838444Z 	at org.apache.dubbo.registry.client.migration.MigrationInvoker.migrateToApplicationFirstInvoker(MigrationInvoker.java:239)
2021-10-20T13:28:53.6842415Z 	at org.apache.dubbo.registry.client.migration.MigrationRuleHandler.refreshInvoker(MigrationRuleHandler.java:73)
2021-10-20T13:28:53.6845753Z 	at org.apache.dubbo.registry.client.migration.MigrationRuleHandler.doMigrate(MigrationRuleHandler.java:57)
2021-10-20T13:28:53.6848930Z 	at org.apache.dubbo.registry.client.migration.MigrationRuleListener.onRefer(MigrationRuleListener.java:241)
2021-10-20T13:28:53.6852265Z 	at org.apache.dubbo.registry.integration.RegistryProtocol.interceptInvoker(RegistryProtocol.java:529)
2021-10-20T13:28:53.6855117Z 	at org.apache.dubbo.registry.integration.RegistryProtocol.doRefer(RegistryProtocol.java:498)
2021-10-20T13:28:53.6857492Z 	at org.apache.dubbo.registry.integration.RegistryProtocol.refer(RegistryProtocol.java:483)
2021-10-20T13:28:53.6860176Z 	at org.apache.dubbo.qos.protocol.QosProtocolWrapper.refer(QosProtocolWrapper.java:83)
2021-10-20T13:28:53.6862490Z 	at org.apache.dubbo.rpc.protocol.ProtocolListenerWrapper.refer(ProtocolListenerWrapper.java:74)
2021-10-20T13:28:53.6865071Z 	at org.apache.dubbo.rpc.cluster.filter.ProtocolFilterWrapper.refer(ProtocolFilterWrapper.java:71)
2021-10-20T13:28:53.6867853Z 	at org.apache.dubbo.rpc.protocol.ProtocolSerializationWrapper.refer(ProtocolSerializationWrapper.java:52)
2021-10-20T13:28:53.6870057Z 	at org.apache.dubbo.rpc.Protocol$Adaptive.refer(Protocol$Adaptive.java)
2021-10-20T13:28:53.6872000Z 	at org.apache.dubbo.config.ReferenceConfig.createInvokerForRemote(ReferenceConfig.java:474)
2021-10-20T13:28:53.6874192Z 	at org.apache.dubbo.config.ReferenceConfig.createProxy(ReferenceConfig.java:379)
2021-10-20T13:28:53.6875945Z 	at org.apache.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:266)
2021-10-20T13:28:53.6877534Z 	at org.apache.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:203)
2021-10-20T13:28:53.6879403Z 	at org.apache.dubbo.config.utils.SimpleReferenceCache.get(SimpleReferenceCache.java:117)
2021-10-20T13:28:53.6881786Z 	at org.apache.dubbo.config.deploy.DefaultModuleDeployer.lambda$referServices$6(DefaultModuleDeployer.java:326)
2021-10-20T13:28:53.6883898Z 	at java.util.concurrent.ConcurrentHashMap$ValuesView.forEach(ConcurrentHashMap.java:4707)
2021-10-20T13:28:53.6886142Z 	at org.apache.dubbo.config.deploy.DefaultModuleDeployer.referServices(DefaultModuleDeployer.java:306)
2021-10-20T13:28:53.6888758Z 	at org.apache.dubbo.config.deploy.DefaultModuleDeployer.start(DefaultModuleDeployer.java:146)
2021-10-20T13:28:53.6892449Z 	at org.apache.dubbo.config.spring.context.DubboDeployApplicationListener.onContextRefreshedEvent(DubboDeployApplicationListener.java:108)
2021-10-20T13:28:53.6897335Z 	at org.apache.dubbo.config.spring.context.DubboDeployApplicationListener.onApplicationEvent(DubboDeployApplicationListener.java:98)
2021-10-20T13:28:53.6901894Z 	at org.apache.dubbo.config.spring.context.DubboDeployApplicationListener.onApplicationEvent(DubboDeployApplicationListener.java:44)

详细日志见：https://github.com/apache/dubbo/runs/3951950812?check_suite_focus=true

类似的失败构建日志有很多，比如这个也是： https://github.com/apache/dubbo/runs/3959438481?check_suite_focus=true

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

Environment

• Dubbo version: 3.0.4
• Operating System version: window10
• Java version: 8
• nacosclient：2.0.0
• dubbo-registry-nacos: 3.0.4
• dubbo-spring-boot-starter: 3.0.4

Steps to reproduce this issue

1. 使用triple协议，启动provider，然后启动consumer
2. 调用一次服务，此时rpc调用正常
3. 重启provider服务，并重启consumer服务
4. 调用此前正常的服务，则抛出异常 Directory already destroyed

在dubbo的服务注册缓存文件cache目录下的文件已经达到了900M System.getProperty ("user.home") + "/.dubbo/dubbo-registry-" + url.getHost () + ".cache" 对比其他正常服务器，正常文件大小只有1-2M，打开这个900M的文件其中很多内容为 \u0000, 由于dubbo默认每隔10分钟会读取这个文件，由于文件太大，导致每次读取造成频繁的GC最终致使JVM在这个时间段内CPU负载非常高而无法处理业务请求。 通过DUMP内存，发现内存泄露都是线程 java.lang.Thread @ 0x779569808 DubboSaveRegistryCache-thread-1 其中同样类似的线程还有2个，每个线程占用200-300M 另外还有大对象 com.alibaba.dubbo.registry.zookeeper.ZookeeperRegistry 3个无法回收，200M左右一个 总计1.5G大小内存无法释放！

为何会有如此大的缓存文件？为何同样的文件会被不同的线程多次加载？

Dubbo版本2.7.7和3.0.0都有这个问题。 目前发现DubboReference注解中不增加URL并指定IP和端口，消费端就无法访问生产端。提示生产端不存在或是列入了黑名单 1、如果要在URL中指定IP和端口，对于增加生产端的灵活性是不是就降底，对于消费端来说应该是透明的。 2、在application.yml配置文件中是否有什么特别的配置可以去掉DubboReference中的url配置 @DubboReference(version = "${platform.service.version}", url = "dubbo://127.0.0.1:12316", lazy = true)

目前我的配置 生产端配置 dubbo: application: id: ${spring.application.name} name: ${spring.application.name} register-mode: instance service-discovery: migration: FORCE_APPLICATION qos-enable: false qos-accept-foreign-ip: false scan: base-packages: com.dd.modules,com.dd.framework registry: # file: ${user.home}/dubbo-cache/${spring.application.name}/dubbo.cache address: nacos://${nacos.host}:${nacos.port}/?registry-type=service monitor: protocol: registry protocol: name: dubbo port: 12316 server: netty4 serialization: kryo provider: retries: 0 delay: -1 timeout: 12000 consumer: timeout: 12000 check: false # 服务启动时检查被调用服务是否可用 client: netty4 retries: 0 # 服务调用重试次数

消费端配置 dubbo: application: id: ${spring.application.name} name: ${spring.application.name} service-discovery: migration: FORCE_APPLICATION qos-enable: false qos-accept-foreign-ip: false registry: # file: ${user.home}/dubbo-cache/${spring.application.name}/dubbo.cache address: nacos://${nacos.host}:${nacos.port} monitor: protocol: registry protocol: name: dubbo port: 12316 server: netty4 serialization: kryo consumer: timeout: 12000 check: false # 服务启动时检查被调用服务是否可用 client: netty4 retries: 0 # 服务调用重试次数

Environment

• Dubbo version: 2.7.14
• Operating System version: win,centos
• Java version: jdk8 & jdk11

Steps to reproduce this issue

for 1, n do

1. instance = ReferenceConfig.get();
2. call instance.func() success();
3. ReferenceConfig.destroy() end

the exchangeclient no close. the connects = n * set connects

Expected Result

ReferenceConfig set connects = 5 and the connect session size = 5 * n the exchange client resource no gc.

Actual Result

in my case, the old-gen use too much and full gc call frequently

now i find two problem

1. transfer layer, close exception

have two same service(hotload ReferenceConfig), notify each other then 2. Registration Center notify and close session will connect again, and new ReferenceConfig will connect, so the connect session size also = 5 * n

Environment

• Dubbo version: 2.7.8
• Operating System version: CentOs7.6
• Java version: 1.8

Steps to reproduce this issue

1. 服务A和服务B互为生产者和消费者，用Nacos作注册中心
2. 服务A重启，重启完毕后服务B调用服务A时报错
3. 主要错误信息：message can not send, because channel is closed
4. 目前的临时解决办法：重启服务B，恢复正常(重启导致服务不稳定，望解决)

stack info

01/03/2023 11:04:17 ERROR [http-nio-8685-exec-3]c.c.l.c.a.BaseExceptionHandlerAdvice - Failed to invoke the method getApprovalTodoCount in the service com.ctrod.cvoon.rpc.AdminRpcManager. Tried 3 times of the providers [10.1.138.65:20882] (1/1) from the registry 10.1.138.65:8848 on the consumer 10.1.138.65 using the dubbo version 2.7.8. Last error is: Failed to invoke remote method: getApprovalTodoCount, provider: dubbo://10.1.138.65:20882/com.ctrod.cvoon.rpc.AdminRpcManager?anyhost=true&application=LiveCloudBaseApplication&category=providers&check=false&deprecated=false&dispatcher=message&dubbo=2.0.2&dynamic=true&generic=false&init=false&interface=com.ctrod.cvoon.rpc.AdminRpcManager&metadata-type=remote&methods=getTimeOutMessageSubscribeSettingUserChooseDto,getCorpDto,checkCommunityPermission,getDepartmentMap,getDataPermissionUserIdList,getTimeOutMessageSubscribeSettingDto,getApprovalTodoCount&path=com.ctrod.cvoon.rpc.AdminRpcManager&pid=32612&protocol=dubbo&qos.enable=false&register.ip=10.1.138.65&release=2.7.15&remote.application=ctrod-cvoon-admin&retries=2&revision=1.0.0&service.name=ServiceBean:/com.ctrod.cvoon.rpc.AdminRpcManager&side=consumer&sticky=false&timeout=9000&timestamp=1672715046548, cause: message can not send, because channel is closed . url:dubbo://10.1.138.65:20882/com.ctrod.cvoon.rpc.ApprovalRpcManager?anyhost=true&application=LiveCloudBaseApplication&category=providers&check=false&codec=dubbo&deprecated=false&dispatcher=message&dubbo=2.0.2&dynamic=true&generic=false&heartbeat=60000&init=false&interface=com.ctrod.cvoon.rpc.ApprovalRpcManager&metadata-type=remote&methods=needApprovalAndCheckPermission,cancelApproval,submitApprovalRecord&path=com.ctrod.cvoon.rpc.ApprovalRpcManager&pid=32612&protocol=dubbo&qos.enable=false&register.ip=10.1.138.65&release=2.7.15&remote.application=ctrod-cvoon-admin&retries=2&revision=1.0.0&service.name=ServiceBean:/com.ctrod.cvoon.rpc.ApprovalRpcManager&side=consumer&sticky=false&timeout=9000&timestamp=1672305915260 org.apache.dubbo.rpc.RpcException: Failed to invoke the method getApprovalTodoCount in the service com.ctrod.cvoon.rpc.AdminRpcManager. Tried 3 times of the providers [10.1.138.65:20882] (1/1) from the registry 10.1.138.65:8848 on the consumer 10.1.138.65 using the dubbo version 2.7.8. Last error is: Failed to invoke remote method: getApprovalTodoCount, provider: dubbo://10.1.138.65:20882/com.ctrod.cvoon.rpc.AdminRpcManager?anyhost=true&application=LiveCloudBaseApplication&category=providers&check=false&deprecated=false&dispatcher=message&dubbo=2.0.2&dynamic=true&generic=false&init=false&interface=com.ctrod.cvoon.rpc.AdminRpcManager&metadata-type=remote&methods=getTimeOutMessageSubscribeSettingUserChooseDto,getCorpDto,checkCommunityPermission,getDepartmentMap,getDataPermissionUserIdList,getTimeOutMessageSubscribeSettingDto,getApprovalTodoCount&path=com.ctrod.cvoon.rpc.AdminRpcManager&pid=32612&protocol=dubbo&qos.enable=false&register.ip=10.1.138.65&release=2.7.15&remote.application=ctrod-cvoon-admin&retries=2&revision=1.0.0&service.name=ServiceBean:/com.ctrod.cvoon.rpc.AdminRpcManager&side=consumer&sticky=false&timeout=9000&timestamp=1672715046548, cause: message can not send, because channel is closed . url:dubbo://10.1.138.65:20882/com.ctrod.cvoon.rpc.ApprovalRpcManager?anyhost=true&application=LiveCloudBaseApplication&category=providers&check=false&codec=dubbo&deprecated=false&dispatcher=message&dubbo=2.0.2&dynamic=true&generic=false&heartbeat=60000&init=false&interface=com.ctrod.cvoon.rpc.ApprovalRpcManager&metadata-type=remote&methods=needApprovalAndCheckPermission,cancelApproval,submitApprovalRecord&path=com.ctrod.cvoon.rpc.ApprovalRpcManager&pid=32612&protocol=dubbo&qos.enable=false&register.ip=10.1.138.65&release=2.7.15&remote.application=ctrod-cvoon-admin&retries=2&revision=1.0.0&service.name=ServiceBean:/com.ctrod.cvoon.rpc.ApprovalRpcManager&side=consumer&sticky=false&timeout=9000&timestamp=1672305915260 at org.apache.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:113) at org.apache.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:260) at org.apache.dubbo.rpc.cluster.interceptor.ClusterInterceptor.intercept(ClusterInterceptor.java:47) at org.apache.dubbo.rpc.cluster.support.wrapper.AbstractCluster$InterceptorInvokerNode.invoke(AbstractCluster.java:92) at org.apache.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:88) at org.apache.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:74) at org.apache.dubbo.common.bytecode.proxy2.getApprovalTodoCount(proxy2.java) at com.ctrod.live.cloud.manager.ext.BaseDataManagerImpl.pcIndexStatistics(BaseDataManagerImpl.java:241) at com.ctrod.live.cloud.controller.base.BaseDataController.pcIndexStatistics(BaseDataController.java:170) at sun.reflect.GeneratedMethodAccessor1387.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190) at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:105) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:878) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:792) at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1040) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006) at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898) at javax.servlet.http.HttpServlet.service(HttpServlet.java:626) at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883) at javax.servlet.http.HttpServlet.service(HttpServlet.java:733) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.alibaba.druid.support.http.WebStatFilter.doFilter(WebStatFilter.java:123) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.ctrod.live.cloud.filter.BaseCorsFilter.doFilter(BaseCorsFilter.java:31) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:100) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.springframework.web.filter.FormContentFilter.doFilterInternal(FormContentFilter.java:93) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:201) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:373) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1589) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:750) Caused by: org.apache.dubbo.remoting.RemotingException: message can not send, because channel is closed . url:dubbo://10.1.138.65:20882/com.ctrod.cvoon.rpc.ApprovalRpcManager?anyhost=true&application=LiveCloudBaseApplication&category=providers&check=false&codec=dubbo&deprecated=false&dispatcher=message&dubbo=2.0.2&dynamic=true&generic=false&heartbeat=60000&init=false&interface=com.ctrod.cvoon.rpc.ApprovalRpcManager&metadata-type=remote&methods=needApprovalAndCheckPermission,cancelApproval,submitApprovalRecord&path=com.ctrod.cvoon.rpc.ApprovalRpcManager&pid=32612&protocol=dubbo&qos.enable=false&register.ip=10.1.138.65&release=2.7.15&remote.application=ctrod-cvoon-admin&retries=2&revision=1.0.0&service.name=ServiceBean:/com.ctrod.cvoon.rpc.ApprovalRpcManager&side=consumer&sticky=false&timeout=9000&timestamp=1672305915260 at org.apache.dubbo.remoting.transport.AbstractClient.send(AbstractClient.java:176) at org.apache.dubbo.remoting.transport.AbstractPeer.send(AbstractPeer.java:53) at org.apache.dubbo.remoting.exchange.support.header.HeaderExchangeChannel.request(HeaderExchangeChannel.java:135) at org.apache.dubbo.remoting.exchange.support.header.HeaderExchangeClient.request(HeaderExchangeClient.java:95) at org.apache.dubbo.rpc.protocol.dubbo.ReferenceCountExchangeClient.request(ReferenceCountExchangeClient.java:91) at org.apache.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:105) at org.apache.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:163) at org.apache.dubbo.rpc.protocol.AsyncToSyncInvoker.invoke(AsyncToSyncInvoker.java:52) at org.apache.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:78) at org.apache.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:89) at org.apache.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:83) at org.apache.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:51) at org.apache.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:83) at org.apache.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:69) at org.apache.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:83) at org.apache.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:56) at org.apache.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:82) ... 63 common frames omitted

What is the purpose of the change

optimization log4j

Brief changelog

Verifying this change

Checklist

• [x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• [ ] Each commit in the pull request should have a meaningful subject line and body.
• [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• [ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
• [ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• [ ] Add some description to dubbo-website project if you are requesting to add a feature.
• [ ] GitHub Actions works fine on your own branch.
• [ ] If this contribution is large, please follow the Software Donation Guide.

hi community. For Proto IDL control platform design. I suggest splitting the tasks into the following parts and trying to complete them

• [ ] Dubbo realizes uploading proto files on the provider side and downloading proto files on the consumer side [doing]
• [ ] dubbo-admin implements schema upload interface and basic version management interface
• [ ] dubbo-admin implements maven-based jar package remote management
• [ ] dubbo-admin implements protobuf syntax verification
• [ ] dubbo-admin implements timely compilation of proto files based on janino

In the near future, I will discuss 1 or 2 tasks with @LXPWing conducting collaborative research

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

Ask your question here

dubbo:3.1.1 jdk:11 os: centOS 7.6 配置如下:

dubbo:
  application:
    name: 
    metadata-service-protocol: tri
  registry:
    address: ${NACOS_REGISTER_ADDR}
    group: ${DUBBO_REGISTER_GROUP}
    parameters:
      namespace: ${NACOS_NAMESPACE}
    username: ${NACOS_USERNAME}
    password: ${NACOS_PASSWORD}
  metadata-report:
    address: ${NACOS_REGISTER_ADDR}
  protocol:
    name: ${DUBBO_PROTOCAL_NAME}
    port: ${DUBBO_PROTOCAL_PORT}
    accesslog: false
  consumer:
    filter: dubboFilterConsumer
    check: false
    timeout: ${DUBBO_CONSUMER_TIMEOUT}
    retries: ${DUBBO_CONSUMER_RETRIES}
  provider:
    filter: dubboFilterProvider

代码里面同时使用了rest和 tri 两种协议，直接注解在接口配置上 启动时一直滚动报下面这个错误，

[DUBBO] Failed to get app metadata for revision 3005bae31919d143caf981fc3d373483 for type local from instance 10.70.33.251:9092, dubbo version: 3.1.1, current host: 10.70.34.222 org.apache.dubbo.rpc.RpcException: Fail to invoke remote method: getMetadataInfo, provider: tri://10.70.33.251:50051/org.apache.dubbo.metadata.MetadataService?connections=1&corethreads=2&dubbo=2.0.2&group=demoGroup&port=50051&protocol=tri&release=3.1.1&retries=0&side=provider&threadpool=cached&threads=100&timeout=5000&token=**************************************************, cause: org.apache.dubbo.rpc.StatusRpcException: UNKNOWN : unknown ~~ java.lang.NullPointerException ~~  ~~ RemoteAddress:10.70.33.251:50051 ~~         at org.apache.dubbo.rpc.protocol.AbstractInvoker.waitForResultIfSync(AbstractInvoker.java:282) ~~       at org.apache.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:185) ~~    at org.apache.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:70) ~~       at org.apache.dubbo.rpc.proxy.InvocationUtil.invoke(InvocationUtil.java:55) ~~  at org.apache.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:75) ~~      at org.apache.dubbo.metadata.MetadataServiceDubboProxy0.getMetadataInfo(MetadataServiceDubboProxy0.java) ~~     at org.apache.dubbo.registry.client.metadata.MetadataUtils.getRemoteMetadata(MetadataUtils.java:171) ~~         at org.apache.dubbo.registry.client.AbstractServiceDiscovery.getRemoteMetadata(AbstractServiceDiscovery.java:178) ~~    at org.apache.dubbo.registry.client.event.listener.ServiceInstancesChangedListener.lambda$doOnEvent$2(ServiceInstancesChangedListener.java:158) ~~      at java.base/java.util.Optional.orElseGet(Optional.java:369) ~~         at org.apache.dubbo.registry.client.event.listener.ServiceInstancesChangedListener.doOnEvent(ServiceInstancesChangedListener.java:158) ~~       at org.apache.dubbo.registry.client.event.listener.ServiceInstancesChangedListener.onEvent(ServiceInstancesChangedListener.java:112) ~~         at org.apache.dubbo.registry.client.event.listener.ServiceInstancesChangedListener$AddressRefreshRetryTask.run(ServiceInstancesChangedListener.java:488) ~~     at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~~         at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) ~~        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~~  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~~         at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~~         at java.base/java.lang.Thread.run(Thread.java:829) ~~ Caused by: java.util.concurrent.ExecutionException: org.apache.dubbo.rpc.StatusRpcException: UNKNOWN : unknown ~~ java.lang.NullPointerException ~~  ~~ RemoteAddress:10.70.33.251:50051 ~~       at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395) ~~    at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2022) ~~        at org.apache.dubbo.rpc.AsyncRpcResult.get(AsyncRpcResult.java:195) ~~   at org.apache.dubbo.rpc.protocol.AbstractInvoker.waitForResultIfSync(AbstractInvoker.java:264) ~~       ... 18 more ~~ Caused by: org.apache.dubbo.rpc.StatusRpcException: UNKNOWN : unknown ~~ java.lang.NullPointerException ~~  ~~ RemoteAddress:10.70.33.251:50051 ~~       at org.apache.dubbo.rpc.TriRpcStatus.asException(TriRpcStatus.java:214) ~~      at org.apache.dubbo.rpc.protocol.tri.DeadlineFuture.doReceived(DeadlineFuture.java:134) ~~     at org.apache.dubbo.rpc.protocol.tri.DeadlineFuture.lambda$received$0(DeadlineFuture.java:91) ~~        at org.apache.dubbo.common.threadpool.ThreadlessExecutor$RunnableWrapper.run(ThreadlessExecutor.java:184) ~~     at org.apache.dubbo.common.threadpool.ThreadlessExecutor.waitAndDrain(ThreadlessExecutor.java:103) ~~   at org.apache.dubbo.rpc.AsyncRpcResult.get(AsyncRpcResult.java:193) ~~  ... 19 more

What is the purpose of the change

Try update service discovery for each 1s

• When application is starting, refresh each 30s
• When service is updating, refresh each 5s

Brief changelog

Verifying this change

Checklist

• [x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• [ ] Each commit in the pull request should have a meaningful subject line and body.
• [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• [ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
• [ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• [ ] Add some description to dubbo-website project if you are requesting to add a feature.
• [ ] GitHub Actions works fine on your own branch.
• [ ] If this contribution is large, please follow the Software Donation Guide.