rocketmq INFO closeChannel: close the connection to remote address[192.168.8.185:30911] result: true

Created on 2 Sep 2020  ·  7Comments  ·  Source: apache/rocketmq

BUG REPORT
version:rocketmq-all-4.7.1-bin-release dledger、rocketmq-console-ng-2.0.0.jar 、java8

broker-n*:

brokerClusterName = RaftCluster
brokerName=RaftNode00
listenPort=30911
namesrvAddr=192.168.8.185:9876;192.168.8.190:9876
storePathRootDir=/tmp/rmqstore/node00
storePathCommitLog=/tmp/rmqstore/node00/commitlog
enableDLegerCommitLog=true
dLegerGroup=RaftNode00
dLegerPeers=n0-192.168.8.185:40911;n1-192.168.8.185:40912;n2-192.168.8.185:40913
dLegerSelfId=n0
sendMessageThreadPoolNums=16
brokerIP1=192.168.8.185


The cluster can be started,After successful startup, why does the console keep printing INFO closeChannel:
close the connection to remote address [192.168.8.190:30931] result: true
close the connection to remote address [192.168.8.185:9876] result: true
*
*
*
close the connection to remote address [192.168.8.190:30911] result: true

thanks

bug

Most helpful comment

1、There is a section in MQAdminExtImpl, which will shutdown MqAdminInstance and then close the channel connection after each invocation of RPC interface. The call chain is:
MQAdminInstance.destroyMQAdminInstance()->mqAdminExt.shutdown()->mqClientInstance.shutdown()->mQClientAPIImpl.shutdown()->mQClientAPIImpl.shutdown()->RemotingUtil.closeChannel(channel).
2、The reason for the "ERROR Exception caught: mqAdminExt get broker stats data TOPIC_PUT_NUMS failed" is that the system topic was not filtered out while console dashbord was making statistics. I will submit a PR to slove this problem in rocketmq-externals.

All 7 comments

I modified the " rocketmq-console-ng-2.0.0.jar Dlogging.level.root=WARN", after startup, "close the connection to remote address [192.168.8.185:9876] result: true" did not keep printing Up. But there is a message in the log "ERROR Exception caught: mqAdminExt get broker stats data TOPIC_PUT_NUMS failed",How can I solve this? thanks

Any progress?

Can you help to fix this issue? @zhangjidi2016

ok

1、There is a section in MQAdminExtImpl, which will shutdown MqAdminInstance and then close the channel connection after each invocation of RPC interface. The call chain is:
MQAdminInstance.destroyMQAdminInstance()->mqAdminExt.shutdown()->mqClientInstance.shutdown()->mQClientAPIImpl.shutdown()->mQClientAPIImpl.shutdown()->RemotingUtil.closeChannel(channel).
2、The reason for the "ERROR Exception caught: mqAdminExt get broker stats data TOPIC_PUT_NUMS failed" is that the system topic was not filtered out while console dashbord was making statistics. I will submit a PR to slove this problem in rocketmq-externals.

@zhangjidi2016 Can you put forward a pr to fix this issue? According to our discussion.

@zhangjidi2016 Can you put forward a pr to fix this issue? According to our discussion.

Maybe I can fix it.

Was this page helpful?
0 / 5 - 0 ratings