RocketMQ 解決 No route info of this topic 異常步驟
Exception in thread "main" org.apache.rocketmq.client.exception.MQClientException: No route info for this topic, TopicTest
For more information, please visit the url, http://rocketmq.apache.org/docs/faq/
at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.sendSelectImpl(DefaultMQProducerImpl.java:1031)
at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.send(DefaultMQProducerImpl.java:997)
at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.send(DefaultMQProducerImpl.java:992)
at org.apache.rocketmq.client.producer.DefaultMQProducer.send(DefaultMQProducer.java:389)
at com.example.mq.Producer.main(Producer.java:40)
00:35:20.088 [NettyClientSelector_1] INFO RocketmqRemoting - closeChannel: close the connection to remote address[] result: true
00:35:45.168 [NettyClientSelector_1] INFO RocketmqRemoting - closeChannel: close the connection to remote address[] result: true
00:36:15.161 [NettyClientSelector_1] INFO RocketmqRemoting - closeChannel: close the connection to remote address[] result: true
00:36:45.164 [NettyClientSelector_1] INFO RocketmqRemoting - closeChannel: close the connection to remote address[] result: true
rocketmq運行時提示 No route info of this topic 異常產生的原因可能是
①Broker禁止自動創建Topic，且用戶沒有通過手工方式創建Topic
②Broker沒有正確連接到Name Server
③Producer沒有正確連接到Name Server
首先解決①這種情況，啟動順序要先啟動nameserver，再啟動broker，啟動broker時加上autoCreateTopicEnable=true
例如 nohup sh mqbroker -n localhost:9876 autoCreateTopicEnable=true &
啟動沒有異常檢查下nameserver中是否成功注冊了broker，有兩種方式
第一種、看broker的日志 如果出現形如
2018-02-28 16:21:35 INFO BrokerControllerScheduledThread1 - register broker to name server 192.168.192.129:9876 OK
2018-02-28 16:22:05 INFO BrokerControllerScheduledThread1 - register broker to name server 192.168.192.129:9876 OK
證明已經連接到nameserver上
第二種、 在bin目錄下執行命令sh mqadmin clusterList -n localhost:9876 如果看到
#Cluster Name #Broker Name #BID #Addr #Version #InTPS(LOAD) #OutTPS(LOAD) #PCWait(ms) #Hour #SPACE
DefaultCluster DEFAULT_BROKER 0 192.168.192.129:10911 V4_2_0_SNAPSHOT 0.00(0,0ms) 0.00(0,0ms) 0 422168.55 -1.0000
也是證明已經連接到nameserver上。
如果按前兩步檢查沒有問題，但啟動還是報錯，那么剩下的可能原因是producer無法連接到nameserver，很可能是防火牆的原因 ，要檢驗猜測只需要關閉防火牆，命令為systemctl stop firewalld.service
然后再次驗證，應該已經可以使用了。