dubbo 服务提供者 由于dubbo.jar 引用冲突导致的问题分析以及解决方案

最新推荐文章于 2024-04-25 21:39:54 发布
最新推荐文章于 2024-04-25 21:39:54 发布
阅读量1.7k 收藏
点赞数 1
文章标签： java
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/WUSISI521521/article/details/117092171
版权

项目pom文件：

<!-- 引入spring-boot-starter以及dubbo和curator的依赖 -->
<dependency>
    <groupId>com.alibaba.boot</groupId>
    <artifactId>dubbo-spring-boot-starter</artifactId>
    <version>0.2.0</version>
</dependency>

<dependency>
    <groupId>org.springframework.cloud</groupId>
    <!--<groupId>com.alibaba.cloud</groupId>-->
    <artifactId>spring-cloud-starter-dubbo</artifactId>
</dependency>

springboot 引用的是dubbo2.6.2

springcloud引用的是dubbo2.7.1

 

在项目中的引用是@Service @Refence 是引用的dubbo2.7.1 启动服务提供者  报如下错误。

java.lang.NullPointerException: null
    at org.springframework.cloud.alibaba.dubbo.metadata.repository.DubboServiceMetadataRepository.unexportURL(DubboServiceMetadataRepository.java:284) ~[spring-cloud-alibaba-dubbo-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at java.util.ArrayList.forEach(ArrayList.java:1259) ~[na:1.8.0_271]
    at org.springframework.cloud.alibaba.dubbo.metadata.repository.DubboServiceMetadataRepository.removeDubboMetadataServiceURLs(DubboServiceMetadataRepository.java:190) ~[spring-cloud-alibaba-dubbo-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at org.springframework.cloud.alibaba.dubbo.metadata.repository.DubboServiceMetadataRepository.getDubboMetadataServiceMetadata(DubboServiceMetadataRepository.java:179) ~[spring-cloud-alibaba-dubbo-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at org.springframework.cloud.alibaba.dubbo.autoconfigure.DubboServiceRegistrationAutoConfiguration.attachDubboMetadataServiceMetadata(DubboServiceRegistrationAutoConfiguration.java:170) ~[spring-cloud-alibaba-dubbo-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at org.springframework.cloud.alibaba.dubbo.autoconfigure.DubboServiceRegistrationAutoConfiguration.attachDubboMetadataServiceMetadata(DubboServiceRegistrationAutoConfiguration.java:165) ~[spring-cloud-alibaba-dubbo-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at org.springframework.cloud.alibaba.dubbo.autoconfigure.DubboServiceRegistrationAutoConfiguration.onServiceInstancePreRegistered(DubboServiceRegistrationAutoConfiguration.java:93) ~[spring-cloud-alibaba-dubbo-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_271]
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_271]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_271]
    at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_271]
    at org.springframework.context.event.ApplicationListenerMethodAdapter.doInvoke(ApplicationListenerMethodAdapter.java:261) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.ApplicationListenerMethodAdapter.processEvent(ApplicationListenerMethodAdapter.java:180) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.ApplicationListenerMethodAdapter.onApplicationEvent(ApplicationListenerMethodAdapter.java:142) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:400) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:354) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.cloud.alibaba.dubbo.registry.DubboServiceRegistrationEventPublishingAspect.beforeRegister(DubboServiceRegistrationEventPublishingAspect.java:49) ~[spring-cloud-alibaba-dubbo-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_271]
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_271]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_271]
    at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_271]
    at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:644) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:626) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.aspectj.AspectJMethodBeforeAdvice.before(AspectJMethodBeforeAdvice.java:44) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:55) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:174) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.aspectj.AspectJAfterAdvice.invoke(AspectJAfterAdvice.java:47) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:174) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:688) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.cloud.alibaba.nacos.registry.NacosServiceRegistry$$EnhancerBySpringCGLIB$$2bd5ed31.register(<generated>) ~[spring-cloud-alibaba-nacos-discovery-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.register(AbstractAutoServiceRegistration.java:209) ~[spring-cloud-commons-2.0.1.RELEASE.jar:2.0.1.RELEASE]
    at org.springframework.cloud.alibaba.nacos.registry.NacosAutoServiceRegistration.register(NacosAutoServiceRegistration.java:74) ~[spring-cloud-alibaba-nacos-discovery-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.start(AbstractAutoServiceRegistration.java:108) ~[spring-cloud-commons-2.0.1.RELEASE.jar:2.0.1.RELEASE]
    at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.bind(AbstractAutoServiceRegistration.java:73) ~[spring-cloud-commons-2.0.1.RELEASE.jar:2.0.1.RELEASE]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_271]
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_271]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_271]
    at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_271]
    at org.springframework.context.event.ApplicationListenerMethodAdapter.doInvoke(ApplicationListenerMethodAdapter.java:261) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.ApplicationListenerMethodAdapter.processEvent(ApplicationListenerMethodAdapter.java:180) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.ApplicationListenerMethodAdapter.onApplicationEvent(ApplicationListenerMethodAdapter.java:142) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:400) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:354) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:164) ~[spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140) ~[spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
    at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:780) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
    at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:412) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:333) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:1277) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:1265) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
    at com.qijy.springboot.ProviderApplication.main(ProviderApplication.java:14) [classes/:na]

 

如果是在项目中引用的是dubbo 2.6.2 则会报如下错误：

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2021-05-20 21:38:23.833 ERROR 31680 --- [           main] o.s.boot.SpringApplication               : Application run failed

org.apache.dubbo.rpc.RpcException: Fail to start server(url: dubbo://192.168.202.25:20880/org.springframework.cloud.alibaba.dubbo.service.DubboMetadataService?anyhost=true&application=provider&bind.ip=192.168.202.25&bind.port=20880&channel.readonly.sent=true&codec=dubbo&default.deprecated=false&default.dynamic=false&default.register=true&deprecated=false&dubbo=2.0.2&dynamic=false&generic=false&group=provider&heartbeat=60000&interface=org.springframework.cloud.alibaba.dubbo.service.DubboMetadataService&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&monitor=dubbo%3A%2F%2F127.0.0.1%3A2181%2Forg.apache.dubbo.registry.RegistryService%3Fapplication%3Dprovider%26dubbo%3D2.0.2%26pid%3D31680%26protocol%3Dregistry%26refer%3Dapplication%253Dprovider%2526dubbo%253D2.0.2%2526interface%253Dorg.apache.dubbo.monitor.MonitorService%2526pid%253D31680%2526register.ip%253D192.168.202.25%2526release%253D2.7.1%2526timestamp%253D1621517902979%26registry%3Dzookeeper%26release%3D2.7.1%26timestamp%3D1621517902910&pid=31680&register=true&release=2.7.1&revision=0.2.2.RELEASE&side=provider&timestamp=1621517902913&version=1.0.0) Failed to bind NettyServer on /192.168.202.25:20880, cause: Address already in use: bind
    at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:333) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.openServer(DubboProtocol.java:305) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.export(DubboProtocol.java:288) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:108) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:57) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.qos.protocol.QosProtocolWrapper.export(QosProtocolWrapper.java:63) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.rpc.Protocol$Adaptive.export(Protocol$Adaptive.java) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.registry.integration.RegistryProtocol.lambda$doLocalExport$2(RegistryProtocol.java:220) ~[dubbo-2.7.1.jar:2.7.1]
    at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660) ~[na:1.8.0_271]
    at org.apache.dubbo.registry.integration.RegistryProtocol.doLocalExport(RegistryProtocol.java:218) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.registry.integration.RegistryProtocol.export(RegistryProtocol.java:184) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:106) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:55) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.qos.protocol.QosProtocolWrapper.export(QosProtocolWrapper.java:61) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.rpc.Protocol$Adaptive.export(Protocol$Adaptive.java) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.config.ServiceConfig.doExportUrlsFor1Protocol(ServiceConfig.java:559) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:417) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:375) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.config.ServiceConfig.export(ServiceConfig.java:337) ~[dubbo-2.7.1.jar:2.7.1]
    at org.springframework.cloud.alibaba.dubbo.service.DubboMetadataServiceExporter.export(DubboMetadataServiceExporter.java:82) ~[spring-cloud-alibaba-dubbo-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at org.springframework.cloud.alibaba.dubbo.metadata.repository.DubboServiceMetadataRepository.getDubboMetadataServiceMetadata(DubboServiceMetadataRepository.java:176) ~[spring-cloud-alibaba-dubbo-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at org.springframework.cloud.alibaba.dubbo.autoconfigure.DubboServiceRegistrationAutoConfiguration.attachDubboMetadataServiceMetadata(DubboServiceRegistrationAutoConfiguration.java:170) ~[spring-cloud-alibaba-dubbo-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at org.springframework.cloud.alibaba.dubbo.autoconfigure.DubboServiceRegistrationAutoConfiguration.attachDubboMetadataServiceMetadata(DubboServiceRegistrationAutoConfiguration.java:165) ~[spring-cloud-alibaba-dubbo-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at org.springframework.cloud.alibaba.dubbo.autoconfigure.DubboServiceRegistrationAutoConfiguration.onServiceInstancePreRegistered(DubboServiceRegistrationAutoConfiguration.java:93) ~[spring-cloud-alibaba-dubbo-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_271]
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_271]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_271]
    at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_271]
    at org.springframework.context.event.ApplicationListenerMethodAdapter.doInvoke(ApplicationListenerMethodAdapter.java:261) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.ApplicationListenerMethodAdapter.processEvent(ApplicationListenerMethodAdapter.java:180) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.ApplicationListenerMethodAdapter.onApplicationEvent(ApplicationListenerMethodAdapter.java:142) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:400) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:354) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.cloud.alibaba.dubbo.registry.DubboServiceRegistrationEventPublishingAspect.beforeRegister(DubboServiceRegistrationEventPublishingAspect.java:49) ~[spring-cloud-alibaba-dubbo-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_271]
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_271]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_271]
    at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_271]
    at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:644) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:626) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.aspectj.AspectJMethodBeforeAdvice.before(AspectJMethodBeforeAdvice.java:44) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:55) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:174) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.aspectj.AspectJAfterAdvice.invoke(AspectJAfterAdvice.java:47) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:174) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:688) ~[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.cloud.alibaba.nacos.registry.NacosServiceRegistry$$EnhancerBySpringCGLIB$$f14236a2.register(<generated>) ~[spring-cloud-alibaba-nacos-discovery-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.register(AbstractAutoServiceRegistration.java:209) ~[spring-cloud-commons-2.0.1.RELEASE.jar:2.0.1.RELEASE]
    at org.springframework.cloud.alibaba.nacos.registry.NacosAutoServiceRegistration.register(NacosAutoServiceRegistration.java:74) ~[spring-cloud-alibaba-nacos-discovery-0.2.2.RELEASE.jar:0.2.2.RELEASE]
    at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.start(AbstractAutoServiceRegistration.java:108) ~[spring-cloud-commons-2.0.1.RELEASE.jar:2.0.1.RELEASE]
    at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.bind(AbstractAutoServiceRegistration.java:73) ~[spring-cloud-commons-2.0.1.RELEASE.jar:2.0.1.RELEASE]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_271]
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_271]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_271]
    at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_271]
    at org.springframework.context.event.ApplicationListenerMethodAdapter.doInvoke(ApplicationListenerMethodAdapter.java:261) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.ApplicationListenerMethodAdapter.processEvent(ApplicationListenerMethodAdapter.java:180) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.ApplicationListenerMethodAdapter.onApplicationEvent(ApplicationListenerMethodAdapter.java:142) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:400) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:354) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:164) ~[spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553) ~[spring-context-5.0.9.RELEASE.jar:5.0.9.RELEASE]
    at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140) ~[spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
    at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:780) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
    at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:412) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:333) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:1277) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:1265) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
    at com.qijy.springboot.ProviderApplication.main(ProviderApplication.java:15) [classes/:na]
Caused by: org.apache.dubbo.remoting.RemotingException: Failed to bind NettyServer on /192.168.202.25:20880, cause: Address already in use: bind
    at org.apache.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:69) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.remoting.transport.netty4.NettyServer.<init>(NettyServer.java:69) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.remoting.transport.netty4.NettyTransporter.bind(NettyTransporter.java:32) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.remoting.Transporter$Adaptive.bind(Transporter$Adaptive.java) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.remoting.Transporters.bind(Transporters.java:56) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.remoting.exchange.support.header.HeaderExchanger.bind(HeaderExchanger.java:44) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.remoting.exchange.Exchangers.bind(Exchangers.java:70) ~[dubbo-2.7.1.jar:2.7.1]
    at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:331) ~[dubbo-2.7.1.jar:2.7.1]
    ... 76 common frames omitted
Caused by: java.net.BindException: Address already in use: bind
    at sun.nio.ch.Net.bind0(Native Method) ~[na:1.8.0_271]
    at sun.nio.ch.Net.bind(Net.java:444) ~[na:1.8.0_271]
    at sun.nio.ch.Net.bind(Net.java:436) ~[na:1.8.0_271]
    at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:225) ~[na:1.8.0_271]
    at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:130) ~[netty-all-4.1.29.Final.jar:4.1.29.Final]
    at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:558) ~[netty-all-4.1.29.Final.jar:4.1.29.Final]
    at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1358) ~[netty-all-4.1.29.Final.jar:4.1.29.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:501) ~[netty-all-4.1.29.Final.jar:4.1.29.Final]
    at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:486) ~[netty-all-4.1.29.Final.jar:4.1.29.Final]
    at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:1019) ~[netty-all-4.1.29.Final.jar:4.1.29.Final]
    at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:254) ~[netty-all-4.1.29.Final.jar:4.1.29.Final]
    at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:366) ~[netty-all-4.1.29.Final.jar:4.1.29.Final]
    at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) ~[netty-all-4.1.29.Final.jar:4.1.29.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404) ~[netty-all-4.1.29.Final.jar:4.1.29.Final]
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:446) ~[netty-all-4.1.29.Final.jar:4.1.29.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884) ~[netty-all-4.1.29.Final.jar:4.1.29.Final]
    at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-all-4.1.29.Final.jar:4.1.29.Final]
    at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_271]
 

问题解决方案：

去掉或者排除多余的dubbo版本，就行了，只留其中的一个dubbo版本就不会有问题了，服务正常启动

 

6云子6
关注
  • 1
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
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全套jar包
11-24
dubbo-demo-consumer-2.0.12-assembly.tar , dubbo-demo-provider-2.0.12-assembly.tar,dubbo-monitor-simple-2.0.12-assembly.tar,dubbo-registry-simple-2.0.12-assembly.tar,zookeeper-3.4.2.tar dubbo全套jar包
Dubbo启动报错
m0_67403188的博客
08-14 2516
最近在写一个demo，使用到dubbo服务，在公司测试demo运行是没有问题的，下班的时候项目服务没有停，直接电脑锁屏就回家了，然后晚上回到家再次测试的时候，demo启动报错，出现了error,但是不影响项目的运行，因为是初学dubbo，没有踩过这个坑，困扰了我几个小时，记录下。...
已解决，java.lang.NullPointerException异常的正确解决方法，亲测有效，嘿嘿嘿！！！
最新发布
PythonAigc的博客
04-25 1763
java.lang.NullPointerException（空指针异常）是Java编程中非常常见的运行时异常，它通常发生在尝试调用或操作一个为null的对象引用时。要解决NullPointerException，你需要找到导致对象为null的原因，并确保在访问该对象之前它已经被正确地初始化或赋值。以下是一些解决NullPointerException的常见方法：
Dubbo Failed to bind NettyServer on /192.168.56.1:xx,cause:Address already in use:bind问题解决
旭东怪的博客
10-13 5246
问题描述： Caused by: org.apache.dubbo.remoting.RemotingException: Failed to bind NettyServer on /192.168.56.1:20882, cause: Address already in use: bind 问题分析： 1、当前项目的dubbo端口20882被占用了，导致报错。 dubbo: scan: base-packages: com.basic protocol: ...
org.apache.dubbo.remoting.RemotingException: Failed to bind NettyServer on /192.168.251.44:28081, ca
weixin_42606709的博客
07-19 1863
ip不对，并不是端口被占
dubbo-admin-0.0.1-SNAPSHOT.jar
09-08
dubbo-admin.jar，不需要tomcat，zookeeper127.0.0.1:2181,账户密码都是root
SpringCloud整合Dubbo的源码
之城的专栏
04-02 1428
前言 现在SpringCloud Alibaba 十分热门, dubbo作为阿里的招牌微服务相关的框架,自然整合进入了SpringCloud了. 我找了下官网发现如下的maven依赖. <dependency> <groupId>com.alibaba.cloud</groupId> <artifactId>spring-cloud-starter-dubbo</artifactId> <version>2
【Dubbo+Zookeeper注册服务遇到的坑】老版dubbo admin安装+端口占用+无法开启RPC+java.lang.NoClassDefFoundError解决
波点兔的博客
03-01 2391
如果你确保你的代码没有错，那么百分之80%以上的错来源于版本。 文章目录1 报错 端口占用Caused by: java.net.BindException: Address already in use:bind &&无法开启dubbo报错 org.apache.dubbo.remoting.RemotingException: Failed to bind NettyServer on /192.168.251.44:280812 老版dubbo admin安装3 报错：java.lan
在使用dubbo时远程访问服务提供者的方法时出现空指针异常java.lang.NullPointerException
椰子奶糖的博客
02-16 4762
在使用dubbo时远程访问服务提供者的方法时出现空指针异常java.lang.NullPointerException 错误日志如下： java.lang.NullPointerException at com.atguigu.service.UserService.hello(UserService.java:20) at com.atguigu.ConsumerUserApplicatio...
解决dubbo消费者注入空指针java.lang.NullPointerException的问题
cccfire的博客
06-05 6202
java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.r...
dubbo超时原因以及解决方案
nandao158的博客
03-31 1万+
dubbo超时原因以及解决方案： 1、超时日志： 服务端： Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout. start time: 2017-08-05 18:14:52.751, end time: 2017-08-05 18:14:53.764, client elapsed: 6 ms, server elapsed: 1006 ms, timeout:
org.apache.dubbo.rpc.RpcException: Fail to start server(url: dubbo://192.168.82.190:20882/service
四季轮换叶，一路招摇胜
04-19 1230
org.apache.dubbo.rpc.RpcException: Fail to start server(url: dubbo://192.168.0.9:20882/service.UserI
dubbo 服务调用说明
weixin_43931625的博客
03-17 3351
dubbo 服务调用说明
Dubbo本地jar包本地安装与离线约束
赵广陆
03-01 720
Dubbox的jar包并没有部署到Maven的中央仓库中，大家在Maven的中央仓库中可以查找到Dubbo的最终版本是2.5.3 , 阿里巴巴解散了Dubbo团队后由当当网继续维护此项目，并改名为 Dubbox ,坐标不变，版本变更了，但是并没有提交到中央仓库。 我们现在需要手动将Dubbox的jar包安装到我的本地仓库中。 先将dubbo-2.8.4.jar包放到d:\setup, 然后输入...
Failed to bind NettyServer on /169.254.116.120:20880, cause: Failed to bind to: /0.0.0.0:20880解决方案
sercherxin的博客
09-28 1137
这里写自定义目录标题问题 刚才在启动dubbo服务时遇到的问题，开始只有一个提供服务的模块，都没有问题，后面又多建了一个提供服务的模块后，启动一个能正常启动，启动第二个就一直报错：Failed to bind NettyServer on /169.254.116.120:20880, cause: Failed to bind to: /0.0.0.0:20880，换顺序启动都是第二个无法启动，看着是因为端口的问题，但是在设置里已经把两个服务的端口都改了的 问题 刚才在启动dubbo服务时遇到的问题，开始
SpringBoot 整合Mybatis 和Dubbo
zhouzhiwengang的专栏
08-16 1743
最近编写了一部分SpringBoot的代码，想整理一个基于SpringBoot 的RPC 远程服务调用框架。 第一步：整合SpringBoot和Mybatis,具体参考:https://blog.csdn.net/zhouzhiwengang/article/details/81677256 第二步：整合SpringBoot 和Dubbo. 1、pom.xml 加载dubbo 依赖的jar ...
SpringCloudAlibaba踩坑日记（二）Relying upon circular references is discouraged and they are prohibited by
weixin_43627706的博客
04-15 1677
文章目录前因报错内容解决方案 前因 这俩天闲来无事想搭建一套最新版本的微服务，顺便写博客记录一下，我用的是当前时间(2022-04-14)最新版本 报错内容 Description: The dependencies of some of the beans in the application context form a cycle: com.alibaba.cloud.dubbo.autoconfigure.DubboLoadBalancedRestTemplateAutoConfig
dubbo‐admin‐0.0.1‐snapshot.jar这个jar包怎么来的
08-06
dubbo-admin-0.0.1-snapshot.jar这个jar包是通过以下步骤来获取的： 首先，Dubbo是一个开源的分布式服务框架，dubbo-admin是Dubbo的管理控制台，用于监控和管理Dubbo的各个服务。 要获取dubbo-admin-0.0.1-snapshot.jar这个jar包，可以按照以下步骤进行： 1. 在Dubbo的官方网站上或者在GitHub上找到Dubbo的源代码仓库。 2. 在源代码仓库中，可以找到dubbo-admin这个模块的目录。 3. 进入dubbo-admin的目录中，可以找到pom.xml文件，该文件是用来管理项目的依赖关系。 4. 在pom.xml文件中，会列出dubbo-admin所依赖的其他jar包及其版本号。 5. 根据pom.xml文件中的依赖关系，可以通过Maven工具自动下载所需的jar包。 6. 使用Maven命令或者IDE工具，执行项目的构建操作，自动下载所需的依赖jar包，其中就包括了dubbo-admin-0.0.1-snapshot.jar。 7. 构建成功之后，可以在目标或者构建目录中找到这个jar包。 总结来说，dubbo-admin-0.0.1-snapshot.jar这个jar包是通过Maven工具根据Dubbo源代码中的pom.xml文件中的依赖关系自动获取的。

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值