快捷導(dǎo)航

springboot+dubbo啟動(dòng)項(xiàng)目時(shí)報(bào)錯(cuò) zookeeper not connected的問(wèn)題及解決方案

更新時(shí)間：2023年06月28日 10:32:57 作者：IccBoY

這篇文章主要介紹了springboot+dubbo項(xiàng)目啟動(dòng)項(xiàng)目時(shí)報(bào)錯(cuò) zookeeper not connected的問(wèn)題，本文給大家定位問(wèn)題及解決方案，結(jié)合實(shí)例代碼給大家講解的非常詳細(xì)，需要的朋友可以參考下

現(xiàn)象

項(xiàng)目在公司網(wǎng)絡(luò)啟動(dòng)時(shí)，能正常啟動(dòng)。但通過(guò)vpn連接到公司網(wǎng)絡(luò)時(shí)卻無(wú)法啟動(dòng)報(bào)下面的錯(cuò)誤java.lang.IllegalStateException: zookeeper not connected。

Caused by: java.lang.IllegalStateException: zookeeper not connected
   at org.apache.dubbo.remoting.zookeeper.curator.CuratorZookeeperClient.<init>(CuratorZookeeperClient.java:84)
   at org.apache.dubbo.remoting.zookeeper.curator.CuratorZookeeperTransporter.createZookeeperClient(CuratorZookeeperTransporter.java:26)
   at org.apache.dubbo.remoting.zookeeper.AbstractZookeeperTransporter.connect(AbstractZookeeperTransporter.java:68)
   at org.apache.dubbo.configcenter.support.zookeeper.ZookeeperDynamicConfiguration.<init>(ZookeeperDynamicConfiguration.java:66)
   at org.apache.dubbo.configcenter.support.zookeeper.ZookeeperDynamicConfigurationFactory.createDynamicConfiguration(ZookeeperDynamicConfigurationFactory.java:43)
   at org.apache.dubbo.common.config.configcenter.AbstractDynamicConfigurationFactory.lambda$getDynamicConfiguration$0(AbstractDynamicConfigurationFactory.java:39)
   at java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1705)
   at org.apache.dubbo.common.config.configcenter.AbstractDynamicConfigurationFactory.getDynamicConfiguration(AbstractDynamicConfigurationFactory.java:39)
   at org.apache.dubbo.common.config.configcenter.DynamicConfiguration.getDynamicConfiguration(DynamicConfiguration.java:224)
   at org.apache.dubbo.config.bootstrap.DubboBootstrap.prepareEnvironment(DubboBootstrap.java:1024)
   at org.apache.dubbo.config.bootstrap.DubboBootstrap.startConfigCenter(DubboBootstrap.java:619)
   at org.apache.dubbo.config.bootstrap.DubboBootstrap.initialize(DubboBootstrap.java:521)
   at org.apache.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:244)
   at org.apache.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:206)
   at org.apache.dubbo.config.spring.beans.factory.annotation.ReferenceAnnotationBeanPostProcessor.doGetInjectedBean(ReferenceAnnotationBeanPostProcessor.java:165)
   at com.alibaba.spring.beans.factory.annotation.AbstractAnnotationBeanPostProcessor.getInjectedObject(AbstractAnnotationBeanPostProcessor.java:409)
   at com.alibaba.spring.beans.factory.annotation.AbstractAnnotationBeanPostProcessor$AnnotatedFieldElement.inject(AbstractAnnotationBeanPostProcessor.java:626)
   at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:119)
   at com.alibaba.spring.beans.factory.annotation.AbstractAnnotationBeanPostProcessor.postProcessPropertyValues(AbstractAnnotationBeanPostProcessor.java:179)
   ... 78 common frames omitted
Caused by: java.lang.IllegalStateException: zookeeper not connected
   at org.apache.dubbo.remoting.zookeeper.curator.CuratorZookeeperClient.<init>(CuratorZookeeperClient.java:81)
   ... 96 common frames omitted
Disconnected from the target VM, address: '127.0.0.1:52979', transport: 'socket'

Process finished with exit code 1

猜測(cè)：連接到zookeeper的服務(wù)器網(wǎng)絡(luò)策略不通— 通過(guò)telnet證實(shí)端口網(wǎng)絡(luò)時(shí)通的。該猜測(cè)不成立。

定位問(wèn)題

進(jìn)一步經(jīng)過(guò)報(bào)錯(cuò)的日志，找到對(duì)應(yīng)的源碼。

public class CuratorZookeeperClient extends AbstractZookeeperClient<CuratorZookeeperClient.NodeCacheListenerImpl, CuratorZookeeperClient.CuratorWatcherImpl> {
    protected static final Logger logger = LoggerFactory.getLogger(CuratorZookeeperClient.class);
    private static final String ZK_SESSION_EXPIRE_KEY = "zk.session.expire";
    static final Charset CHARSET = StandardCharsets.UTF_8;
    private final CuratorFramework client;
    private static Map<String, NodeCache> nodeCacheMap = new ConcurrentHashMap<>();
    public CuratorZookeeperClient(URL url) {
        super(url);
        try {
            int timeout = url.getParameter(TIMEOUT_KEY, DEFAULT_CONNECTION_TIMEOUT_MS);
            int sessionExpireMs = url.getParameter(ZK_SESSION_EXPIRE_KEY, DEFAULT_SESSION_TIMEOUT_MS);
            CuratorFrameworkFactory.Builder builder = CuratorFrameworkFactory.builder()
                    .connectString(url.getBackupAddress())
                    .retryPolicy(new RetryNTimes(1, 1000))
                    .connectionTimeoutMs(timeout)
                    .sessionTimeoutMs(sessionExpireMs);
            String authority = url.getAuthority();
            if (authority != null && authority.length() > 0) {
                builder = builder.authorization("digest", authority.getBytes());
            }
            client = builder.build();
            client.getConnectionStateListenable().addListener(new CuratorConnectionStateListener(url));
            client.start();
            boolean connected = client.blockUntilConnected(timeout, TimeUnit.MILLISECONDS);
            if (!connected) {
                throw new IllegalStateException("zookeeper not connected");
            }
        } catch (Exception e) {
            throw new IllegalStateException(e.getMessage(), e);
        }
    }

可以看出是 boolean connected = client.blockUntilConnected(timeout, TimeUnit.MILLISECONDS); 這里 connected 返回了fasle導(dǎo)致的問(wèn)題。然后下端點(diǎn)，發(fā)現(xiàn)timeout = 3000 ，也就說(shuō)3秒內(nèi)需要鏈接成功，否則就會(huì)超時(shí)。

推測(cè)由于vpn的方式連接的 zk服務(wù)器，很有可能是 3秒內(nèi)沒(méi)有得到服務(wù)端的正確響應(yīng)，而導(dǎo)致了異常，然后拋出了異常。

基于上的推測(cè)，將該timeout的默認(rèn)值3000改大一些后，然后就啟動(dòng)成功了。

解決

修改dubbo的配置，下面是springboot的項(xiàng)目，修改的方式。從上面的報(bào)錯(cuò)信息是可以看出是 configcenter的連接超時(shí)。下面配置了三個(gè)配置的超時(shí)時(shí)間，可根據(jù)情況進(jìn)行配置。

dubbo:
config-center:
timeout: 10000
metadata-report:
timeout: 10000
registry:
timeout: 10000

到此這篇關(guān)于springboot+dubbo項(xiàng)目啟動(dòng)項(xiàng)目時(shí)報(bào)錯(cuò) zookeeper not connected的文章就介紹到這了,更多相關(guān)springboot+dubbo啟動(dòng)項(xiàng)目報(bào)錯(cuò) zookeeper not connected內(nèi)容請(qǐng)搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家！

您可能感興趣的文章: