spwangxp opened a new issue #588:
URL: https://github.com/apache/rocketmq-externals/issues/588
**BUG REPORT**
1. Please describe the issue you observed:
- What did you do (The steps to reproduce)?
a) rocketmq 4.5.1, console 1.0.0, produce some msg to specified topic by
console (checked by mqadmin cli).
b) stop all broker nameserver and console.
c) start rocketmq 4.7.1 consoel 1.0.1(build from source), can produce
consume msg normally. but console 1.0.1 cannot provide service.
- What did you expect to see?
console could provide service
- What did you see instead?
the page could be opened, but it seems didn't connected to the nameserver.
but log shows connected.
2. Please tell us about your environment:
ubuntu 16:04 openjdk-8-jdk
3. Other information (e.g. detailed explanation, logs, related issues,
suggestions how to fix, etc):
...
[2020-07-06 17:25:00.105] INFO closeChannel: close the connection to remote
address[172.23.5.24:9876] result: true
[2020-07-06 17:25:00.109] INFO closeChannel: close the connection to remote
address[172.23.5.22:10911] result: true
[2020-07-06 17:25:00.113] INFO closeChannel: close the connection to remote
address[172.23.5.23:10911] result: true
[2020-07-06 17:25:30.019] INFO shutdown thread PullMessageService interrupt
true
[2020-07-06 17:25:30.019] INFO join thread PullMessageService eclipse
time(ms) 0 90000
[2020-07-06 17:25:30.019] INFO closeChannel: close the connection to remote
address[172.23.5.24:9876] result: true
[2020-07-06 17:25:30.020] INFO closeChannel: close the connection to remote
address[172.23.5.23:10911] result: true
[2020-07-06 17:25:30.020] INFO shutdown thread RebalanceService interrupt
false
[2020-07-06 17:25:30.020] INFO join thread RebalanceService eclipse
time(ms) 0 90000
[2020-07-06 17:25:30.120] INFO closeChannel: close the connection to remote
address[172.23.5.22:10911] result: true
[2020-07-06 17:26:00.003] INFO shutdown thread PullMessageService interrupt
true
[2020-07-06 17:26:00.004] INFO join thread PullMessageService eclipse
time(ms) 0 90000
[2020-07-06 17:26:00.004] INFO shutdown thread RebalanceService interrupt
false
[2020-07-06 17:26:00.004] INFO join thread RebalanceService eclipse
time(ms) 0 90000
[2020-07-06 17:26:00.009] INFO shutdown thread PullMessageService interrupt
true
[2020-07-06 17:26:00.009] INFO join thread PullMessageService eclipse
time(ms) 0 90000
[2020-07-06 17:26:00.010] INFO shutdown thread RebalanceService interrupt
false
[2020-07-06 17:26:00.010] INFO join thread RebalanceService eclipse
time(ms) 0 90000
[2020-07-06 17:26:00.013] INFO shutdown thread PullMessageService interrupt
true
[2020-07-06 17:26:00.013] INFO join thread PullMessageService eclipse
time(ms) 0 90000
[2020-07-06 17:26:00.013] INFO shutdown thread RebalanceService interrupt
false
[2020-07-06 17:26:00.014] INFO join thread RebalanceService eclipse
time(ms) 0 90000
[2020-07-06 17:26:00.104] INFO closeChannel: close the connection to remote
address[172.23.5.24:9876] result: true
[2020-07-06 17:26:00.110] INFO closeChannel: close the connection to remote
address[172.23.5.22:10911] result: true
[2020-07-06 17:26:00.113] INFO closeChannel: close the connection to remote
address[172.23.5.23:10911] result: true
[2020-07-06 17:26:30.017] INFO shutdown thread PullMessageService interrupt
true
[2020-07-06 17:26:30.018] INFO join thread PullMessageService eclipse
time(ms) 0 90000
[2020-07-06 17:26:30.018] INFO closeChannel: close the connection to remote
address[172.23.5.24:9876] result: true
[2020-07-06 17:26:30.018] INFO closeChannel: close the connection to remote
address[172.23.5.23:10911] result: true
[2020-07-06 17:26:30.018] INFO shutdown thread RebalanceService interrupt
false
[2020-07-06 17:26:30.018] INFO join thread RebalanceService eclipse
time(ms) 0 90000
[2020-07-06 17:26:30.118] INFO closeChannel: close the connection to remote
address[172.23.5.22:10911] result: true
... (above repeat times)
----------------------------------------------------------------
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:
[email protected]
