记一次坑爹的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的内容
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | 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
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | 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 |
以上设置完毕之后检查没有问题了,还要关闭
1 2 | producer.setVipChannelEnabled( false ); producer.setSendMsgTimeout( 50000 ); |
这个超时的问题如果不设置,默认很快超时也会报错误。
【推荐】国内首个AI IDE,深度理解中文开发场景,立即下载体验Trae
【推荐】编程新体验,更懂你的AI,立即体验豆包MarsCode编程助手
【推荐】抖音旗下AI助手豆包,你的智能百科全书,全免费不限次数
【推荐】轻量又高性能的 SSH 工具 IShell:AI 加持,快人一步
· 探究高空视频全景AR技术的实现原理
· 理解Rust引用及其生命周期标识(上)
· 浏览器原生「磁吸」效果!Anchor Positioning 锚点定位神器解析
· 没有源码,如何修改代码逻辑?
· 一个奇形怪状的面试题:Bean中的CHM要不要加volatile?
· 分享4款.NET开源、免费、实用的商城系统
· 全程不用写代码,我用AI程序员写了一个飞机大战
· MongoDB 8.0这个新功能碉堡了,比商业数据库还牛
· 白话解读 Dapr 1.15:你的「微服务管家」又秀新绝活了
· 上周热点回顾(2.24-3.2)
2019-11-05 并发中如何保证缓存DB双写一致性(JAVA栗子)