Before Creating the Bug Report
Runtime platform environment
CentOS 7.9
RocketMQ version
RocketMQ Server: 5.3.0、5.3.2
RocketMQ Client: 5.3.0
JDK Version
JDK 1.8.0_461
Describe the Bug
Updating consumer points using the remoting port of RocketMQ 5.3.0 client timed out. But everything is normal on the broker port。
Attempted to replace with the following issue fix versions, but none of them resolved the issue:
Issue: 7199
Issue: 7238
Issue: 9630
Steps to Reproduce
- The client code is as follows:
DefaultMQAdminExt newAdmin = new DefaultMQAdminExt();
newAdmin.setNamesrvAddr(NEW_NAMESRV);
newAdmin.setInstanceName("offset-target-" + consumerGroup);
newAdmin.setVipChannelEnabled(false);
newAdmin.start();
// update target rocketmq offset
newAdmin.updateConsumeOffset(BROKER_ADDR, consumerGroup, “broker-0”, "0");
- The output result is as follows：
org.apache.rocketmq.remoting.exception.RemotingTimeoutException: wait response on the channel </192.168.0.10:30006> timeout, 4919(ms)
at org.apache.rocketmq.remoting.netty.NettyRemotingAbstract.invokeSyncImpl(NettyRemotingAbstract.java:504)
at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:555)
at org.apache.rocketmq.client.impl.MQClientAPIImpl.updateConsumerOffset(MQClientAPIImpl.java:1489)
at org.apache.rocketmq.tools.admin.DefaultMQAdminExtImpl.updateConsumeOffset(DefaultMQAdminExtImpl.java:1732)
at org.apache.rocketmq.tools.admin.DefaultMQAdminExt.updateConsumeOffset(DefaultMQAdminExt.java:699)
at com.demo.RocketMQMigrationApp.migrateOffsets(RocketMQMigrationApp.java:137)
at com.demo.RocketMQMigrationApp.main(RocketMQMigrationApp.java:45)
- rmq-proxy.json
{
"rocketMQClusterName": "DefaultCluster",
"namesrvAddr": "192.168.0.10:30000",
"grpcServerPort": 30005,
"remotingListenPort": 30006
}
- Even after extending the timeout period, the update still fails
DefaultMQAdminExt newAdmin = new DefaultMQAdminExt(100000L);
...
- Except for the remoting.log, there is no log information for other modules
2025-09-08 17:43:46 INFO NettyServerNIOSelector_1 - NETTY SERVER PIPELINE: channelInactive, the channel[10.11.0.18:11292]
2025-09-08 17:43:46 INFO NettyServerNIOSelector_1 - NETTY SERVER PIPELINE: channelUnregistered, the channel[10.11.0.18:11292]
- If the above port is switched to a broker port, everything will be normal。Sending and receiving messages using the remoting port are both normal。
What Did You Expect to See?
Updating consumer points using the remoting port is normal
What Did You See Instead?
Running the following method timed out
newAdmin.updateConsumeOffset(BROKER_ADDR, consumerGroup, “broker-0”, "0");
Additional Context
No response
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
CentOS 7.9
RocketMQ version
RocketMQ Server: 5.3.0、5.3.2
RocketMQ Client: 5.3.0
JDK Version
JDK 1.8.0_461
Describe the Bug
Updating consumer points using the remoting port of RocketMQ 5.3.0 client timed out. But everything is normal on the broker port。
Attempted to replace with the following issue fix versions, but none of them resolved the issue:
Issue: 7199
Issue: 7238
Issue: 9630
Steps to Reproduce
What Did You Expect to See?
Updating consumer points using the remoting port is normal
What Did You See Instead?
Running the following method timed out
Additional Context
No response