在搭建好zookeeper集群之后(3台),使用sh zkServer.sh status
命令已经可以查看到各个节点的身份,两个follower一个leader,没毛病。但是启动tomcat服务的时候,后台总是报异常,说是找不到服务,启动dubbo监控中心也是看不到任何服务。
于是登录到zookeeper节点中,挨个使用sh bin/zkCli.sh
命令查看,果不其然,leader节点出现了问题,在登录客户端之后不断的报一组socket连接失败的异常:
2019-06-22 14:05:48,246 [myid:] - INFO [main-SendThread(localhost:2181):ClientCnxn$SendThread@1025] - Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
2019-06-22 14:05:48,250 [myid:] - INFO [main-SendThread(localhost:2181):ClientCnxn$SendThread@1162] - Socket error occurred: localhost/127.0.0.1:2181: Connection refused
2019-06-22 14:05:49,352 [myid:] - INFO [main-SendThread(localhost:2181):ClientCnxn$SendThread@1025] - Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
2019-06-22 14:05:49,360 [myid:] - INFO [main-SendThread(localhost:2181):ClientCnxn$SendThread@1162] - Socket error occurred: localhost/127.0.0.1:2181: Connection refused
2019-06-22 14:05:50,462 [myid:] - INFO [main-SendThread(localhost:2181):ClientCnxn$SendThread@1025] - Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
2019-06-22 14:05:50,464 [myid:] - INFO [main-SendThread(localhost:2181):ClientCnxn$SendThread@1162] - Socket error occurred: localhost/127.0.0.1:2181: Connection refused
……
然后查看该节点的配置文件conf/zoo.cfg
,发现竟然鬼使神差的将leader节点的clientPort写成了2182!(正常情况下集群内所有节点的端口都应该是2181)
于是将端口号改过来,重启服务。这下3台节点都正常了,再次重启Tomcat服务
……然鹅……
……还是不行……
但是这次从dubbo监控中心发现了consumer,说明zk集群已经没毛病了,可能是dubbo服务本身的问题,于是开始看provider的注解和配置文件是否有问题:
查看Service注解:
没毛病,确实是dubbo的Service注解
再查看yml文件:
乍一看好像没啥问题,其实是光写了scan,而没写basePackage!难怪扫不到!
改成:
终于搞定!
真是千里之堤,溃于蚁穴啊!程序员的僧命里有一半时间都是在与脑残失误做斗争……(笑哭)