记一次坑爹的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);
这个超时的问题如果不设置,默认很快超时也会报错误。