大家好，我是烤鴨：
?? ?今天分享一下使用dubbo遇到的幾個問題。

1. cause: KeeperErrorCode = ConnectionLoss for /dubbo/ xxx

異常如下：

pid=9965&qos.accept.foreign.ip=false&qos.enable=true&qos.port=10887&timestamp=1567416737107, cause: KeeperErrorCode = ConnectionLoss for /dubbo/com.etc.service.bank.IEtcBankcardCodeService/providers/dubbo%3A%2F%2F172.17.33.68%3A20887%2Fcom.etc.service.bank.IEtcBankcardCodeService%3Fanyhost%3Dtrue%26application%3Detc-manage-service-customer%26default.timeout%3D600000%26dubbo%3D2.6.2%26generic%3Dfalse%26interface%3Dcom.etc.service.bank.IEtcBankcardCodeService%26methods%3Dupdate%2Cinsert%2CselectListByObject%2CselectBankCodes%2CselectBank%2CselectOneByObject%26pid%3D9965%26revision%3D1.2.0%26side%3Dprovider%26timestamp%3D1567416870108at com.alibaba.dubbo.registry.zookeeper.ZookeeperRegistry.doRegister(ZookeeperRegistry.java:116)at com.alibaba.dubbo.registry.support.FailbackRegistry.retry(FailbackRegistry.java:315)at com.alibaba.dubbo.registry.support.FailbackRegistry$1.run(FailbackRegistry.java:68)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748)

可以考慮看下這篇文章：
https://blog.csdn.net/xsm666/article/details/85258450
我們zk是3個節(jié)點(diǎn)的集群配置，修改了如下zoo.cfg的配置

tickTime=10000 initLimit=1000

2. Will not attempt to authenticate using SASL (unknown error)

[INFO] [main-SendThread(172.17.33.77:2181)] [2019-09-03 11:29:46,048] ?logStartConnect(1032) | Opening socket connection to server 172.17.33.77/172.17.33.77:2181. Will not attempt to authenticate using SASL (unknown error) [WARN] [main-SendThread(172.17.33.77:2181)] [2019-09-03 11:29:46,049] ?run(1162) | Session 0x1034bacf7d90005 for server null, unexpected error, closing socket connection and attempting reconnect java.net.ConnectException: Connection refusedat sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1141)

關(guān)閉防火墻。

servcie iptables stop???????

https://www.cnblogs.com/hfultrastrong/p/7876198.html

3. No provider available from registry：

[ERROR] [DubboServerHandler-172.17.33.68:20887-thread-68] [2019-09-04 13:39:26,308] ?invoke(85) | ?[DUBBO] Got unchecked and undeclared exception which called by 172.17.33.68. service: com.etc.service.customer.IEtcCustomerService, method: getCustomerNewType, exception: com.alibaba.dubbo.rpc.RpcException: No provider available from registry 172.17.33.68:2181 for service com.etc.service.credit.EtcCreditApplyLogService on consumer 172.17.33.68 use dubbo version 2.6.2, please check status of providers(disabled, not registered or in blacklist)., dubbo version: 2.6.2, current host: 172.17.33.68 com.alibaba.dubbo.rpc.RpcException: No provider available from registry 172.17.33.68:2181 for service com.etc.service.credit.EtcCreditApplyLogService on consumer 172.17.33.68 use dubbo version 2.6.2, please check status of providers(disabled, not registered or in blacklist).at com.alibaba.dubbo.registry.integration.RegistryDirectory.doList(RegistryDirectory.java:575)at com.alibaba.dubbo.rpc.cluster.directory.AbstractDirectory.list(AbstractDirectory.java:74)at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.list(AbstractClusterInvoker.java:271)at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:232)at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:75)at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52)at com.alibaba.dubbo.common.bytecode.proxy1.queryIsNewCustomerUrl(proxy1.java)at com.etc.service.customer.EtcCustomerServiceImpl.getCustomerNewType(EtcCustomerServiceImpl.java:873)at com.etc.service.customer.EtcCustomerServiceImpl$$FastClassBySpringCGLIB$$2f308333.invoke(<generated>)at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:746)at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:294)at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:98)at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:688)at com.etc.service.customer.EtcCustomerServiceImpl$$EnhancerBySpringCGLIB$$953f1998.getCustomerNewType(<generated>)at com.alibaba.dubbo.common.bytecode.Wrapper15.invokeMethod(Wrapper15.java)at com.alibaba.dubbo.rpc.proxy.javassist.JavassistProxyFactory$1.doInvoke(JavassistProxyFactory.java:47)at com.alibaba.dubbo.rpc.proxy.AbstractProxyInvoker.invoke(AbstractProxyInvoker.java:76)at com.alibaba.dubbo.config.invoker.DelegateProviderMetaDataInvoker.invoke(DelegateProviderMetaDataInvoker.java:52)at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:56)at com.alibaba.dubbo.rpc.filter.ExceptionFilter.invoke(ExceptionFilter.java:62)at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75)at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)at com.alibaba.dubbo.rpc.filter.TimeoutFilter.invoke(TimeoutFilter.java:42)at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)at com.alibaba.dubbo.rpc.protocol.dubbo.filter.TraceFilter.invoke(TraceFilter.java:78)at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)at com.alibaba.dubbo.rpc.filter.ContextFilter.invoke(ContextFilter.java:72)at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)at com.alibaba.dubbo.rpc.filter.GenericFilter.invoke(GenericFilter.java:131)at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)at com.alibaba.dubbo.rpc.filter.ClassLoaderFilter.invoke(ClassLoaderFilter.java:38)at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)at com.alibaba.dubbo.rpc.filter.EchoFilter.invoke(EchoFilter.java:38)at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol$1.reply(DubboProtocol.java:103)at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.handleRequest(HeaderExchangeHandler.java:96)at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.received(HeaderExchangeHandler.java:172)at com.alibaba.dubbo.remoting.transport.DecodeHandler.received(DecodeHandler.java:51)at com.alibaba.dubbo.remoting.transport.dispatcher.ChannelEventRunnable.run(ChannelEventRunnable.java:80)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748)

這個比較明顯就是，提供者的服務(wù)找不到，看下 dubbo-admin里邊，服務(wù)是否注入成功。
dubbo-admin 鏈接: https://pan.baidu.com/s/139VlS82K1u76lPT0Q4UjrA 提取碼: ed3a?

4. 項(xiàng)目啟動后，拉取生產(chǎn)者時巨慢。一個項(xiàng)目啟動半小時才能完整啟動，并且訪問時還獲取不到生產(chǎn)者的服務(wù)。

notify(387) | ?[DUBBO] Notify urls for subscribe url provider: xxx retry(366) | ?[DUBBO] Failed to retry subscribe xxx

去 dubbo-admin查看服務(wù)的生產(chǎn)和消費(fèi)均正常，就是奇怪的地方在于一個服務(wù)同一個ip項(xiàng)目有多個消費(fèi)者（應(yīng)該只有一個）。
jps| grep 項(xiàng)目
發(fā)現(xiàn)同一個項(xiàng)目啟動多個，這是dubbo-admin上看到多個消費(fèi)者的原因。
猜想是多個服務(wù)同時啟動并獲取 zk上的服務(wù)，導(dǎo)致獲取阻塞。
至于為什么同時啟動多個，應(yīng)該是jenkins每次集成顯示成功后jar包并未啟動成功，然后又集成,持續(xù)了好幾次。

dubbo項(xiàng)目啟動 zookeeper 發(fā)布和訂閱特別慢。
因?yàn)閦k是要往服務(wù)器寫日志的，這時候檢查一下服務(wù)器的io。

iostat -x

查看io讀寫情況。

雖然不確定是不是這個問題，切換一個機(jī)器部署zk，解決了。
新機(jī)器的io情況。

如果出現(xiàn) dubbo項(xiàng)目啟動特別慢，拉取 zookeeper 服務(wù)日志打印特別慢的情況。考慮換一臺機(jī)器部署zk，有可能是服務(wù)器的io問題。

總結(jié)

以上是生活随笔為你收集整理的Will not attempt to authenticate using SASL | dubbo项目启动特别慢，拉取 zookeeper 服务日志打印特别慢的全部內(nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯，歡迎將生活随笔推薦給好友。