qsrg opened a new issue, #10289: URL: https://github.com/apache/rocketmq/issues/10289
### 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/discussions). - [x] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/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. ### Runtime platform environment centos7 ### RocketMQ version 4.x、5.x ### JDK Version jdk8 ### Describe the Bug When the client enables the VIP port function (vipChannelEnabled=true), the client always sends heartbeats to the broker's non VIP port, while other operations (such as message sending ) use the VIP port. This results in the connection to the VIP port not having heartbeat maintenance, being considered idle by the broker and closed. At the same time, any message sent will timeout due to the connection being closed. ### Steps to Reproduce producer.setVipChannelEnabled(true); Send a message every 2 minutes ### What Did You Expect to See? When the VIP port function is enabled, the heartbeat should also be sent to the VIP port to maintain the active connection status of the VIP port and avoid message sending timeout caused by idle connection closure. ### What Did You See Instead? Even if the client uses the VIP port, heartbeats always use the non-VIP port, resulting in the following issues: No heartbeat maintenance for connections on the VIP port The broker closes VIP port connections as it regards them as idle The client encounters a timeout error when sending messages at the moment the connection is closed broker：close the connection <img width="4030" height="246" alt="Image" src="https://github.com/user-attachments/assets/ccc7557e-dfbc-4f31-9475-b0b4eefbf13c"; /> producer: is sending a message but timeout <img width="2421" height="592" alt="Image" src="https://github.com/user-attachments/assets/06f09717-6741-4d98-9578-92d14738c112"; /> ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
