jkoChen opened a new issue, #15725: URL: https://github.com/apache/dubbo/issues/15725
### Pre-check - [x] I am sure that all the content I provide is in English. ### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar issues. ### Apache Dubbo Component Java SDK (apache/dubbo) ### Dubbo Version Dubbo 3.3.5 JDK21 When dubbo.consumer.check=false, and when the client executes the connect() in org.apache.dubbo.remoting.transport.AbstractClient#AbstractClient(org.apache.dubbo.common.URL, org.apache.dubbo.remoting.ChannelHandler), if a certain Provider is killed at this time, the consumer side will keep reconnecting and print the following logs: <img width="2433" height="286" alt="Image" src="https://github.com/user-attachments/assets/c48925f6-cfde-4792-be1d-5dc7680213d3"; /> ### Steps to reproduce this issue 1. Start more than one Provider 2. Configure dubbo.consumer.check=false for the Consumer 3. Set a breakpoint at line 93 of org.apache.dubbo.remoting.transport.AbstractClient 4. Run the Consumer in debug mode 5. When the code reaches line 93 of org.apache.dubbo.remoting.transport.AbstractClient, execute kill -9 on one of the Providers 6. Resume the Consumer, and you will see it keeps reconnecting and print error log ### What you expected to happen When the Invoker is still being created, a Provider offline notification is received, which causes the Invoker being created to not be properly destroyed. This is just my guess, and I haven't had time to carefully check the corresponding logic. ### Anything else _No response_ ### Are you willing to submit a pull request to fix on your own? - [ ] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
