lollipopjin opened a new issue, #903: URL: https://github.com/apache/rocketmq-clients/issues/903
### Before Creating the Bug Report - [X] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq-clients/discussions). - [X] I have searched the [GitHub Issues](https://github.com/apache/rocketmq-clients/issues) and [GitHub Discussions](https://github.com/apache/rocketmq-clients/discussions) of this repository and believe that this is not a duplicate. - [X] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Programming Language of the Client Rust ### Runtime Platform Environment Mac OS 15.2.0 ### RocketMQ Version of the Client/Server RocketMQ 5.3.1 with Proxy cluster mode. ### Run or Compiler Version _No response_ ### Describe the Bug The SimpleConsumer's sync settings show an error after the connection is closed by the server side. The error message is as follows: `Jan 03 11:44:11.935 ERRO[src/client.rs:201:33] sync settings failed: failed to call rpc: Failed to send message via channel at session.update_settings => failed to send telemetry command, source: channel closed, component: client` However, at the same time, I am still able to receive messages, as shown in the attached image.  ### Steps to Reproduce 1）Start the RocketMQ server with the Proxy. 2）Start a simple consumer using Cargo (note: handle exceptions by receiving messages and continue with retries). 3）Restart the Proxy. ### What Did You Expect to See? The sync settings should be restored after the proxy is restarted. ### What Did You See Instead? The SimpleConsumer's sync settings show an error after the connection is closed by the server side. ### Additional Context _No response_ -- 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: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
