fcabbage commented on issue #15880: URL: https://github.com/apache/dubbo/issues/15880#issuecomment-3695313211
Sorry for not seeing your message in a timely manner. Based on the above demo, I tested the 3.3.6 version. When the provider goes offline, the consumer no longer reports reconnection errors. **But**, the configuration **dubbo.protocol.preferred-protocol=tri** seems to have been invalidated — there is only one channel using the Dubbo protocol between the consumer and the provider. In this case, when the provider goes offline, the destroy method of the consumer's Dubbo invoker will shut down the reconnection task, hence no error is reported. In the version 3.3.0, this problem occurred because there were two channels between the consumer and the provider, and all calls were made only through the **Triple invoker**. Could you tell me how to prioritize the use of Triple when the consumer does not specify a protocol in version 3.3.6? P.S. The reason I do not specify a protocol in the consumer is that I am in the transition period of upgrading from Dubbo 2 to Dubbo 3. -- 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]
