AlbumenJ commented on issue #14938: URL: https://github.com/apache/dubbo/issues/14938#issuecomment-2522042216
> @AlbumenJ I am using Dubbo 3.2.3 in the test environment. The issue is that the instance-level offline notification for the ServiceDiscoveryRegistryDirectory has come, but the interface-level notification for RegistryDirectory has not, resulting in the counter of ReferenceCountExchangeClient not being zero.Could you tell me how the refreshInvoker in RegistryDirectory can be triggered? Is there a sequence of events between ServiceDiscoveryRegistryDirectory and RegistryDirectory? Due to some class deletion issues, I cannot upgrade beyond version 3.2.3. The maximum version I can currently use is 3.2.3. Can you tell me what code was modified to fix this problem? Regarding the provider going offline, I am not directly executing "ApplicationModel.defaultModel().destroy()". Instead, I first execute "Offline offline = new Offline(ApplicationModel.defaultModel().getFrameworkModel()); offline.execute(null, null);", and after waiting for 10 seconds, I then execute "ApplicationModel.default Model().destroy()." —————————————————————————————————————————————————————— 我在测试环境就是使用3.2.3的dubbo，现在的问题就是ServiceDisCoveryRegistrydirectory实例级的下线通知来了，但是RegistryDirectory 接口级的通知没有，导致ReferenceCountExchangeClient的计数器不为0。能不能跟我说下，RegistryDirectory的refreshInvoker怎么才能被触发呢？ServiceDisCoveryRegistrydirectory和RegistryDirectory 有没有先后关系？ 由于一些类删除问题，导致我不能再升级超过3.2.3。现状能使用最大的版本只能是3.2.3。能否告诉我，修改了什么代码从而修复这个问题。对应provider下线，我不是直接执行 ApplicationModel.defaultModel().destroy() 的。而是先执行了 Offline offline = new Offline(ApplicationModel.defaultModel().getFrameworkModel());offline.execute(null, null); 等� �10秒之后才执行 ApplicationModel.defaultModel().destroy()。 We have fixed couple of bugs about connections in 3.2.x and it is hard to figure out which. :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
