XIACYBING commented on issue #13450: URL: https://github.com/apache/dubbo/issues/13450#issuecomment-1846480457
> > > I think we can destroy all the clients before destroy DubboProtocol to prevent this error. > > > > > > Will closing the SharedClientsProvider before the DubboProtocol cause any call issues? Because the DubboInvoker are still providing services to the consumer. > > Can we should check the type of ClientsProvider before destroy in DubboInvoker, and all SharedClientsProvider should manage by DubboProtocol. > > Before DubboProtocol destroyed, all the DubboInvoker should have been destroyed. So, we can make sure all the DubboInvokers being destroyed and DubboProtocol will not print error message. I don't quite understand. The current situation is to destroy the DubboProtocol first and then the DubboInvokers. Should we modify it to destroy the DubboInvokers first and then the DubboProtocol? And when destroying the DubboProtocol, should we continue to destroy the SharedClientsProvider? -- 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]
