You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2020/09/02 04:00:24 UTC
[GitHub] [rocketmq] wangyingdong opened a new issue #2285: rocketmq INFO closeChannel: close the connection to remote address[192.168.8.185:30911] result: true
wangyingdong opened a new issue #2285:
URL: https://github.com/apache/rocketmq/issues/2285
**BUG REPORT**
version：rocketmq-all-4.7.1-bin-release dledger、rocketmq-console-ng-2.0.0.jar 、java8
**broker-n0:**
---------------------
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
-----------------------
After successful startup, why does the console keep printing INFO closeChannel: close the Connection to Remote Address [192.168.8.190:30931] Result: true
thanks
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] zhangjidi2016 commented on issue #2285: rocketmq INFO closeChannel: close the connection to remote address[192.168.8.185:30911] result: true
Posted by GitBox <gi...@apache.org>.
zhangjidi2016 commented on issue #2285:
URL: https://github.com/apache/rocketmq/issues/2285#issuecomment-695788409
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.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] zongtanghu commented on issue #2285: rocketmq INFO closeChannel: close the connection to remote address[192.168.8.185:30911] result: true
Posted by GitBox <gi...@apache.org>.
zongtanghu commented on issue #2285:
URL: https://github.com/apache/rocketmq/issues/2285#issuecomment-694722380
Any progress?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] zongtanghu commented on issue #2285: rocketmq INFO closeChannel: close the connection to remote address[192.168.8.185:30911] result: true
Posted by GitBox <gi...@apache.org>.
zongtanghu commented on issue #2285:
URL: https://github.com/apache/rocketmq/issues/2285#issuecomment-694724057
Can you help to fix this issue? @zhangjidi2016
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] mark4z commented on issue #2285: rocketmq INFO closeChannel: close the connection to remote address[192.168.8.185:30911] result: true
Posted by GitBox <gi...@apache.org>.
mark4z commented on issue #2285:
URL: https://github.com/apache/rocketmq/issues/2285#issuecomment-725808330
> @zhangjidi2016 Can you put forward a pr to fix this issue? According to our discussion.
Maybe I can fix it.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] wangyingdong commented on issue #2285: rocketmq INFO closeChannel: close the connection to remote address[192.168.8.185:30911] result: true
Posted by GitBox <gi...@apache.org>.
wangyingdong commented on issue #2285:
URL: https://github.com/apache/rocketmq/issues/2285#issuecomment-686174460
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
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] zongtanghu commented on issue #2285: rocketmq INFO closeChannel: close the connection to remote address[192.168.8.185:30911] result: true
Posted by GitBox <gi...@apache.org>.
zongtanghu commented on issue #2285:
URL: https://github.com/apache/rocketmq/issues/2285#issuecomment-701263325
@zhangjidi2016 Can you put forward a pr to fix this issue? According to our discussion.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] zhangjidi2016 commented on issue #2285: rocketmq INFO closeChannel: close the connection to remote address[192.168.8.185:30911] result: true
Posted by GitBox <gi...@apache.org>.
zhangjidi2016 commented on issue #2285:
URL: https://github.com/apache/rocketmq/issues/2285#issuecomment-694725632
ok
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] zhangjidi2016 commented on issue #2285: rocketmq INFO closeChannel: close the connection to remote address[192.168.8.185:30911] result: true
Posted by GitBox <gi...@apache.org>.
zhangjidi2016 commented on issue #2285:
URL: https://github.com/apache/rocketmq/issues/2285#issuecomment-695788409
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.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org