Dubbo启动报错

最新推荐文章于 2024-07-02 00:50:11 发布
最新推荐文章于 2024-07-02 00:50:11 发布
阅读量2.4k 收藏
点赞数 1
分类专栏： java 文章标签： dubbo java 分布式 后端 c++
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/m0_67403188/article/details/126328039
版权

异常关键字：

  • ERROR com.alibaba.dubbo.remoting.transport.AbstractClient - [DUBBO] Failed to start NettyClient
  • com.alibaba.dubbo.remoting.RemotingException: client
  • at com.alibaba.dubbo.remoting.transport.netty.NettyClient.doConnect(NettyClient.java:127)
  • client-side timeout 3000ms (elapsed: 3002ms) from netty client 10.0.0.3 using dubbo version 2.5.3

最近在写一个demo，使用到dubbo服务，在公司测试demo运行是没有问题的，下班的时候项目服务没有停，直接电脑锁屏就回家了，然后晚上回到家再次测试的时候，demo启动报错，出现了error,但是不影响项目的运行，因为是初学dubbo，没有踩过这个坑，困扰了我几个小时，记录下

异常信息：

23:31:40.962 [RMI TCP Connection(3)-127.0.0.1] ERROR com.alibaba.dubbo.remoting.transport.AbstractClient -  [DUBBO] Failed to start NettyClient XPS-13/10.0.0.3 connect to the server /10.63.73.141:20880 (check == false, ignore and retry later!), cause: client(url: dubbo://10.63.73.141:20880/com.ryan.service.StudentDubboService?anyhost=true&application=dubbo&check=false&codec=dubbo&connections=1&dubbo=2.5.3&heartbeat=60000&interface=com.ryan.service.StudentDubboService&logger=slf4j&methods=findStudentInfoByStuId,insertStudent,deleteStudentByStuId,findStudentListByPage,updateStudentByStuId&payload=51557050&pid=19596&retries=0&revision=1.0-SNAPSHOT&side=consumer&timeout=60000&timestamp=1527607895642&version=1.0.0) failed to connect to server /10.63.73.141:20880 client-side timeout 3000ms (elapsed: 3002ms) from netty client 10.0.0.3 using dubbo version 2.5.3, dubbo version: 2.5.3, current host: 10.0.0.3
com.alibaba.dubbo.remoting.RemotingException: client(url: dubbo://10.63.73.141:20880/com.ryan.service.StudentDubboService?anyhost=true&application=dubbo&check=false&codec=dubbo&connections=1&dubbo=2.5.3&heartbeat=60000&interface=com.ryan.service.StudentDubboService&logger=slf4j&methods=findStudentInfoByStuId,insertStudent,deleteStudentByStuId,findStudentListByPage,updateStudentByStuId&payload=51557050&pid=19596&retries=0&revision=1.0-SNAPSHOT&side=consumer&timeout=60000&timestamp=1527607895642&version=1.0.0) failed to connect to server /10.63.73.141:20880 client-side timeout 3000ms (elapsed: 3002ms) from netty client 10.0.0.3 using dubbo version 2.5.3
	at com.alibaba.dubbo.remoting.transport.netty.NettyClient.doConnect(NettyClient.java:127) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.remoting.transport.AbstractClient.connect(AbstractClient.java:280) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.remoting.transport.AbstractClient.<init>(AbstractClient.java:103) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.remoting.transport.netty.NettyClient.<init>(NettyClient.java:61) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.remoting.transport.netty.NettyTransporter.connect(NettyTransporter.java:37) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.remoting.Transporter$Adpative.connect(Transporter$Adpative.java) ~[?:2.5.3]
	at com.alibaba.dubbo.remoting.Transporters.connect(Transporters.java:67) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchanger.connect(HeaderExchanger.java:37) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.remoting.exchange.Exchangers.connect(Exchangers.java:102) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.initClient(DubboProtocol.java:378) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.getClients(DubboProtocol.java:323) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.refer(DubboProtocol.java:303) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.refer(ProtocolFilterWrapper.java:62) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.refer(ProtocolListenerWrapper.java:65) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.rpc.Protocol$Adpative.refer(Protocol$Adpative.java) ~[?:2.5.3]
	at com.alibaba.dubbo.registry.integration.RegistryDirectory.toInvokers(RegistryDirectory.java:395) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.registry.integration.RegistryDirectory.refreshInvoker(RegistryDirectory.java:224) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.registry.integration.RegistryDirectory.notify(RegistryDirectory.java:195) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.registry.support.AbstractRegistry.notify(AbstractRegistry.java:449) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.registry.support.FailbackRegistry.doNotify(FailbackRegistry.java:273) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.registry.support.FailbackRegistry.notify(FailbackRegistry.java:259) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.registry.zookeeper.ZookeeperRegistry.doSubscribe(ZookeeperRegistry.java:170) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.registry.support.FailbackRegistry.subscribe(FailbackRegistry.java:189) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.registry.integration.RegistryDirectory.subscribe(RegistryDirectory.java:133) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.registry.integration.RegistryProtocol.doRefer(RegistryProtocol.java:271) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.registry.integration.RegistryProtocol.refer(RegistryProtocol.java:254) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.refer(ProtocolFilterWrapper.java:60) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.refer(ProtocolListenerWrapper.java:63) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.rpc.Protocol$Adpative.refer(Protocol$Adpative.java) ~[?:2.5.3]
	at com.alibaba.dubbo.config.ReferenceConfig.createProxy(ReferenceConfig.java:392) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:300) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:138) ~[dubbo-2.5.3.jar:2.5.3]
	at com.alibaba.dubbo.config.spring.ReferenceBean.getObject(ReferenceBean.java:65) ~[dubbo-2.5.3.jar:2.5.3]
	at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:168) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:103) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1517) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:251) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.findAutowireCandidates(DefaultListableBeanFactory.java:1120) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1044) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:942) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:533) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:88) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:331) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1202) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:537) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:303) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:299) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:755) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:757) ~[spring-context-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:480) ~[spring-context-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:403) ~[spring-web-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:306) ~[spring-web-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:106) ~[spring-web-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4853) ~[catalina.jar:8.0.47]
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314) ~[catalina.jar:8.0.47]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) ~[catalina.jar:8.0.47]
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753) ~[catalina.jar:8.0.47]
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:729) ~[catalina.jar:8.0.47]
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717) ~[catalina.jar:8.0.47]
	at org.apache.catalina.startup.HostConfig.manageApp(HostConfig.java:1733) ~[catalina.jar:8.0.47]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_144]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_144]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_144]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_144]
	at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300) ~[tomcat-coyote.jar:8.0.47]
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) ~[?:1.8.0_144]
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) ~[?:1.8.0_144]
	at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:484) ~[catalina.jar:8.0.47]
	at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:433) ~[catalina.jar:8.0.47]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_144]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_144]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_144]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_144]
	at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300) ~[tomcat-coyote.jar:8.0.47]
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) ~[?:1.8.0_144]
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) ~[?:1.8.0_144]
	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468) ~[?:1.8.0_144]
	at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76) ~[?:1.8.0_144]
	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309) ~[?:1.8.0_144]
	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401) ~[?:1.8.0_144]
	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829) ~[?:1.8.0_144]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_144]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_144]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_144]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_144]
	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) ~[?:1.8.0_144]
	at sun.rmi.transport.Transport$1.run(Transport.java:200) ~[?:1.8.0_144]
	at sun.rmi.transport.Transport$1.run(Transport.java:197) ~[?:1.8.0_144]
	at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_144]
	at sun.rmi.transport.Transport.serviceCall(Transport.java:196) ~[?:1.8.0_144]
	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568) ~[?:1.8.0_144]
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826) ~[?:1.8.0_144]
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683) ~[?:1.8.0_144]
	at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_144]
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682) [?:1.8.0_144]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_144]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_144]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_144]
[2018-05-29 11:31:43,755] Artifact doorstore-web:war exploded: Artifact is deployed successfully
[2018-05-29 11:31:43,755] Artifact doorstore-web:war exploded: Deploy took 26,723 milliseconds

问题解决

1、之前发牢骚的时候已经讲过，这个demo在公司运行没有问题，下班的时候没有关闭demo,即dubbo服务正常注册
2、dubbo注册中心(zookeeper)用的是公网地址
3、在家运行demo，启动dubbo报错，但项目能正常启动、dubbo服务正常注册，而且demo能正常运行，丝毫不受报错信息的影响

图为dubbo-admin中的信息截图

提供者信息

消费者信息

找了很多资料，最终发现是因为dubbo消费者无法连接到生产者提供的服务（内网IP ），如上图，两个提供者消费者，两个IP都为路由器分配的内网IP，即消费者在寻找提供者的时候，其中一个提供者地址不具有可连通性，这个内网是不具有可达性的，所以找不到服务的提供者，导致最终报错，所以问题的根源不在dubbo的配置上，只需要处于同一网络环境下，那么就能避免这个问题

m0_67403188
关注
  • 1
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
解决dubbo启动报错的问题
01-28
解决dubbo启动报错，加载失败问题。
解决dubbo启动的时候报错，无法读取方案文档 'http://code.alibabatech.com/schema/dubbo/dubbo.xsd'
03-30
解决启动dubbo项目的时候出现，无法读取方案文档 'http://code.alibabatech.com/schema/dubbo/dubbo.xsd'，其实在你本地把dubbo.jar文件解压，然后在META-INF下边就有个dubbo.xsd，就是他
Dubbo报错解决方案
u013425005的博客
02-27 759
“C:\Program Files\Java\jdk1.8.0_171\bin\java.exe” -agentlib:jdwp=transport=dt_socket,address=127.0.0.1:54051,suspend=y,server=n -DSTOP.PORT=0 -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxrem...
org.apache.dubbo 2.7.7 服务发布注册源码
吴振照
09-29 814
org.apache.dubbo服务注册原理源码分析： 　　本文主要针对dubbo-spring-boot-starter 2.7.7版本, 对应的 org.apache.dubbo 2.7.7 版本的源码。 　　本文主要从以下几个点来分析： 前置知识点--Dubbo的SPI机制。 服务发布注册的入口。 服务发布源码分析 服务注册源码分析。 Dubbo的SPI机制： 　　没接...
Mac中idea调用Dubbo出现以下报错
awei970512的博客
11-14 508
WARN | DubboSaveMetadataReport-thread-1 | org.apache.dubbo.metadata.store.nacos.NacosMetadataReport:189 | [DUBBO] Failed to save service store file, cause: Operation not permitted, dubbo version: X.X.XX, current host: 地址。
publish nacos metadata failed
qq_34369766的博客
01-05 1万+
publish nacos metadata failed 系统环境参考上一篇的服务搭建 Dubbo 3.0.3 + Nacos 2.0.3 + Spring Boot 2.3.6.RELEASE 整合及使用时遇到的问题 参考本地的配置方式，将容器云环境的服务中的配置文件进行配置替换后，启动并没有想象的那么顺利，服务启动后程序出现如下错误。 2022-01-05 10:38:43.565 ERROR 1 --- [Report-thread-1] o.a.d.m.store.nacos.NacosMetad
dubbo2.7.3使用过程问题集合
热门推荐
zsx18273117003的博客
09-11 1万+
一、IOException parsing XML document from class path resource [com/zsx/provider.xml]; nested exception is java.io.FileNotFoundException: class path resource [com/zsx/provider.xml] cannot be opened becau...
dubbo 服务提供者 由于dubbo.jar 引用冲突导致的问题分析以及解决方案
WUSISI521521的博客
05-20 1686
项目pom文件： <!-- 引入spring-boot-starter以及dubbo和curator的依赖 --> <dependency> <groupId>com.alibaba.boot</groupId> <artifactId>dubbo-spring-boot-starter</artifactId> <version>0.2.0</version> </depend
dubbo解析-详解元数据中心MetadataReport
龚厂长的博客
05-18 1万+
元数据中心是dubbo2.7版本之后新增的功能，主要是为了减轻注册中心的压力，将部分存储在注册中心的内容放到元数据中心。元数据中心的数据只是给自己使用的，改动不需要告知对端，比如服务端修改了元数据，不需要通知消费端。这样注册中心存储的数据减少，同时大大降低了因为配置修改导致注册中心频繁通知监听者，从而大大减轻注册中心的压力。 本文将介绍如何配置启用元数据中心，还会介绍其实现原理并解析代码
解决dubbo-admin在jdk1.8下启动报错
11-16
解决dubbo-admin在jdk1.8下启动报错问题，需要下载dubbo源码修改问题重新编译打包发布，这里已经和重新编译。
解决dubbo引用xsd报错
07-05
dubbo找不到dubbo.xsd报错 Eclipse配置 选择windows-->preferrence-->xml->xmlcatalog-->add->catalog entry -->file system,选择模版文件（本地下载的）后，修改key值为...
Dubbo3之服务发布注册与订阅
程序员小潘
08-24 501
Dubbo 在 2.7 之前的版本只配备了注册中心，主流使用的注册中心为 zookeeper。后来 2.7 版本官方进行了三大中心的改造，分别是：注册中心、元数据中心、配置中心。元数据定义为描述数据的数据，在服务治理中，例如服务接口名，重试次数，版本号等等都可以理解为元数据。。Dubbo 2.7 进行了大刀阔斧的改动，只将真正属于服务治理的数据发布到注册中心之中，大大降低了注册中心的压力；同时，将全量的元数据发布到另外的元数据中心；配置中心主要是外部化配置的集中存储。
Dubbo 3.x源码(9)—Dubbo启动元数据中心源码
终生学习践行者
08-21 686
基于Dubbo 3.1，详细介绍了Dubbo启动元数据中心源码。
Dubbo Admin整合Nacos、Dubbo
qq_42739776的博客
04-11 4176
1.服务提供者 1.依赖 版本号为2.2.7.REALEASE <dependency> <groupId>com.alibaba.cloud</groupId> <artifactId>spring-cloud-starter-dubbo</artifactId> </dependency> 2.配置文件 网上大多数配置都是用的zookeeper，笔者之
dubbo生产者篇
qq_37436172的博客
05-06 1077
启动流程 注解@EnableDubbo 注解内分别导入
package org.apache.dubbo.metadata.report； import org.apache.dubbo.common.extension.ExtensionLoader；
爱音乐的程序猿的博客
01-21 2482
问题描述： 之前做的使用dubbo得项目后台突然启动不了了，项目报错 package org.apache.dubbo.metadata.report; import org.apache.dubbo.common.extension.ExtensionLoader; public class MetadataReportFactory$Adaptive implements org.apache.dubbo.metadata.report.MetadataReportFactory { public or
解决：[DUBBO] Failed to start NettyClient LAPTOP-OA5V6BNU/10.21.67.39 connect to the server /192.168.问题
SELECT_BIN的博客
12-24 1万+
报错： 2018-12-24 15:53:59.752 WARN 36460 --- [ main] c.a.d.remoting.transport.AbstractClient : [DUBBO] Failed to start NettyClient LAPTOP-OA5V6BNU/10.21.67.39 connect to the server /192.1...
10.javaSE基础_JDBC编译程序(Driver+Statement+Connection+mysql数据库连接)
最新发布
m0_61086522的博客
07-02 1161
JDBC是的缩写。它是Sun的Javasoft公司制定的Java数据库连接技术，是一套标准接口java.sql包中提供了JDBC API,通过它连接到各种数据库系统，编写访问数据库的程序。JDBC API不能直接访问数据库，它依赖于数据库厂商提供的JDBC Driver（JDBC驱动程序）
springboot dubbo整合 项目启动报错Property 'mapperLocations' was not specified.
09-19
根据提供的引用内容，错误信息"Property 'mapperLocations' was not specified"表明在springboot dubbo整合项目启动时没有指定'mapperLocations'属性。这通常是因为配置文件中没有正确设置该属性导致的。 为了解决这个问题，你可以按照以下步骤进行操作： 1. 确保你的项目中存在mybatis或其他持久化框架，并且已配置了相应的数据库连接信息和mapper文件路径。 2. 在你的application.properties或application.yml配置文件中添加'mapperLocations'属性，并指定正确的mapper文件路径。例如： ``` # application.properties mybatis.mapper-locations=classpath:mapper/*.xml # application.yml mybatis: mapper-locations: classpath:mapper/*.xml ``` 这里的'mapper/*.xml'应该是你实际的mapper文件所在的路径。 3. 确保你的mapper文件正确放置在指定的路径下，且文件名以'.xml'结尾。 完成以上步骤后，重新启动项目，应该可以正常加载mapper文件并解决报错问题。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值