記一次坑爹的Rocketmq排錯

 

 

 還有萬惡的

No route info of this topic

這一類錯誤 按照網上說的聲明的

autoCreateTopicEnable=true

設置之後多沒用明顯的錯誤該報錯繼續報錯，這裏記錄一下 ，排錯方案，由於我的是docker搭建的服務，先創建出來docker-compose

version: '2.1'
services:
  rmqnamesrv-a:
    image: rocketmqinc/rocketmq:4.3.0
    privileged: true
    container_name: rmqnamesrv-a
    ports:
      - 9876:9876
    volumes:
      - ./data/logs/nameserver-a:/opt/logs
      - ./data/store/nameserver-a:/opt/store
    command: sh mqnamesrv
    networks:
        rmq:
          aliases:
            - rmqnamesrv-a

  rmqbroker-a:
    image: rocketmqinc/rocketmq:4.3.0
    privileged: true
    container_name: rmqbroker-a
    ports:
      - 10911:10911
    volumes:
      - ./data/logs/broker-a:/opt/logs
      - ./data/store/broker-a:/opt/store
      - ./data/brokerconf/broker-a.conf:/opt/rocketmq-4.3.0/conf/broker.conf 
    environment:
        TZ: Asia/Shanghai
        JAVA_OPTS: " -Duser.home=/opt"
        JAVA_OPT_EXT: "-server -Xms256m -Xmx256m -Xmn256m"
    command: sh mqbroker -c /opt/rocketmq-4.3.0/conf/broker.conf autoCreateTopicEnable=true &
    links:
      - rmqnamesrv-a:rmqnamesrv-a
    networks:
      rmq:
        aliases:
          - rmqbroker-a

  rmqbroker-b:
    image: rocketmqinc/rocketmq:4.3.0
    privileged: true
    container_name: rmqbroker-b
    ports:
      - 10909:10909
      - 10907:10907
    volumes:
      - ./data/logs/broker-b:/opt/logs
      - ./data/store/broker-b:/opt/store
      - ./data/brokerconf/broker-b.conf:/opt/rocketmq-4.3.0/conf/broker.conf 
    environment:
        TZ: Asia/Shanghai
        JAVA_OPTS: " -Duser.home=/opt"
        JAVA_OPT_EXT: "-server -Xms256m -Xmx256m -Xmn256m"
    command: sh mqbroker -c /opt/rocketmq-4.3.0/conf/broker.conf autoCreateTopicEnable=true &
    links:
      - rmqnamesrv-a:rmqnamesrv-a
    networks:
      rmq:
        aliases:
          - rmqbroker-b
  rmqconsole:
    image: styletang/rocketmq-console-ng
    privileged: true
    container_name: rmqconsole
    ports:
      - 8080:8080
    environment:
        JAVA_OPTS: -Drocketmq.namesrv.addr=rmqnamesrv-a:9876 -Dcom.rocketmq.sendMessageWithVIPChannel=false
    networks:
      rmq:
        aliases:
          - rmqconsole
networks:
  rmq:
    name: rmq
    driver: bridge

 

   PS:rocketmq內有個vip通道，默認是設置監聽的端口 - 2

進入容器後，關閉防火牆，在容器內 我們判斷是否可以連接

 

 以上連接輸出是沒有問題的，如果一旦有報錯，就去檢查你的broker到nameserver之間是否通信成功吧，貼進去broker的內容

brokerClusterName = rocketmq-cluster
brokerName = broker-a
brokerId = 0
brokerIP1 = 192.168.1.223
deleteWhen = 04
fileReservedTime = 48
# 內網的(阿里雲有內網IP和外網IP)
namesrvAddr=192.168.1.223:9876
autoCreateTopicEnable=true
#Broker 對外服務的監聽端口,
listenPort = 10911
#Broker角色
#- ASYNC_MASTER 異步複製Master
#- SYNC_MASTER 同步雙寫Master
#- SLAVE
brokerRole=ASYNC_MASTER
#刷盤方式
#- ASYNC_FLUSH 異步刷盤
#- SYNC_FLUSH 同步刷盤
flushDiskType=ASYNC_FLUSH

　　broker-b

brokerClusterName = rocketmq-cluster
brokerName = broker-b
brokerId = 0
brokerIP1 =192.168.1.223
deleteWhen = 04
fileReservedTime = 48
# 內網的(阿里雲有內網IP和外網IP)
namesrvAddr=192.168.1.223:9876
autoCreateTopicEnable=true
#Broker 對外服務的監聽端口,
listenPort = 10909
#Broker角色
#- ASYNC_MASTER 異步複製Master
#- SYNC_MASTER 同步雙寫Master
#- SLAVE
brokerRole=ASYNC_MASTER
#刷盤方式
#- ASYNC_FLUSH 異步刷盤
#- SYNC_FLUSH 同步刷盤
flushDiskType=ASYNC_FLUSH

　　以上設置完畢之後檢查沒有問題了，還要關閉

 

producer.setVipChannelEnabled(false);
producer.setSendMsgTimeout(50000);

　　

這個超時的問題如果不設置，默認很快超時也會報錯誤。