少年的白日梦 2022-06-23 09:56 采纳率: 0%
浏览 304

关于Springboot集成dubbo时,yaml配置文件失效的问题

使用Springboot搭建Dubbo时,Sprinboot使用的是yaml对dubbo的注册地址等进行了配置,但是配置不生效。
当我使用yaml文件配置了dubbo的一些信息后,在启动类上加上了@EnableDubbo注解,启动项目的时候报端口已被占用的错误。
yaml文件配置的dubbo:

img

使用yaml文件配置dubbo的情况下启动生产者服务报错:

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2022-06-23 09:50:32.375 ERROR 5052 --- [           main] o.s.boot.SpringApplication               : Application run failed

com.alibaba.dubbo.rpc.RpcException: Fail to start server(url: dubbo://10.7.25.50:20880/com.mywork.dubboapi.service.UserService?anyhost=true&application=mywork-provider&bind.ip=10.7.25.50&bind.port=20880&channel.readonly.sent=true&codec=dubbo&dubbo=2.0.1&generic=false&heartbeat=60000&interface=com.mywork.dubboapi.service.UserService&methods=getUser&pid=5052&side=provider&timestamp=1655949031999) Failed to bind NettyServer on /10.7.25.50:20880, cause: Failed to bind to: /0.0.0.0:20880
    at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:274) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.openServer(DubboProtocol.java:251) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.export(DubboProtocol.java:238) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:56) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:93) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.qos.protocol.QosProtocolWrapper.export(QosProtocolWrapper.java:56) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.rpc.Protocol$Adaptive.export(Protocol$Adaptive.java) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.registry.integration.RegistryProtocol.doLocalExport(RegistryProtocol.java:166) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.registry.integration.RegistryProtocol.export(RegistryProtocol.java:129) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:54) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:91) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.qos.protocol.QosProtocolWrapper.export(QosProtocolWrapper.java:54) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.rpc.Protocol$Adaptive.export(Protocol$Adaptive.java) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.config.ServiceConfig.doExportUrlsFor1Protocol(ServiceConfig.java:504) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:356) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:315) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.config.ServiceConfig.export(ServiceConfig.java:214) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.config.spring.ServiceBean.onApplicationEvent(ServiceBean.java:120) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.config.spring.ServiceBean.onApplicationEvent(ServiceBean.java:49) ~[dubbo-2.5.10.jar:2.0.1]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176) ~[spring-context-5.3.20.jar:5.3.20]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169) ~[spring-context-5.3.20.jar:5.3.20]
    at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143) ~[spring-context-5.3.20.jar:5.3.20]
    at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:421) ~[spring-context-5.3.20.jar:5.3.20]
    at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:378) ~[spring-context-5.3.20.jar:5.3.20]
    at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:938) ~[spring-context-5.3.20.jar:5.3.20]
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:586) ~[spring-context-5.3.20.jar:5.3.20]
    at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:147) ~[spring-boot-2.7.0.jar:2.7.0]
    at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:734) [spring-boot-2.7.0.jar:2.7.0]
    at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:408) [spring-boot-2.7.0.jar:2.7.0]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:308) [spring-boot-2.7.0.jar:2.7.0]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:1306) [spring-boot-2.7.0.jar:2.7.0]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:1295) [spring-boot-2.7.0.jar:2.7.0]
    at com.mywork.dubboprovider.DubboProviderApplication.main(DubboProviderApplication.java:13) [classes/:na]
Caused by: com.alibaba.dubbo.remoting.RemotingException: Failed to bind NettyServer on /10.7.25.50:20880, cause: Failed to bind to: /0.0.0.0:20880
    at com.alibaba.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:68) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.remoting.transport.netty.NettyServer.<init>(NettyServer.java:61) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.remoting.transport.netty.NettyTransporter.bind(NettyTransporter.java:31) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.remoting.Transporter$Adaptive.bind(Transporter$Adaptive.java) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.remoting.Transporters.bind(Transporters.java:56) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchanger.bind(HeaderExchanger.java:42) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.remoting.exchange.Exchangers.bind(Exchangers.java:70) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:272) ~[dubbo-2.5.10.jar:2.0.1]
    ... 32 common frames omitted
Caused by: org.jboss.netty.channel.ChannelException: Failed to bind to: /0.0.0.0:20880
    at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:303) ~[netty-3.2.5.Final.jar:na]
    at com.alibaba.dubbo.remoting.transport.netty.NettyServer.doOpen(NettyServer.java:92) ~[dubbo-2.5.10.jar:2.0.1]
    at com.alibaba.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:63) ~[dubbo-2.5.10.jar:2.0.1]
    ... 39 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_281]
    at sun.nio.ch.Net.bind(Net.java:444) ~[na:1.8.0_281]
    at sun.nio.ch.Net.bind(Net.java:436) ~[na:1.8.0_281]
    at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:225) ~[na:1.8.0_281]
    at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) ~[na:1.8.0_281]
    at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind(NioServerSocketPipelineSink.java:148) ~[netty-3.2.5.Final.jar:na]
    at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket(NioServerSocketPipelineSink.java:100) ~[netty-3.2.5.Final.jar:na]
    at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:74) ~[netty-3.2.5.Final.jar:na]
    at org.jboss.netty.channel.Channels.bind(Channels.java:468) ~[netty-3.2.5.Final.jar:na]
    at org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:192) ~[netty-3.2.5.Final.jar:na]
    at org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen(ServerBootstrap.java:348) ~[netty-3.2.5.Final.jar:na]
    at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:176) ~[netty-3.2.5.Final.jar:na]
    at org.jboss.netty.channel.socket.nio.NioServerSocketChannel.<init>(NioServerSocketChannel.java:85) ~[netty-3.2.5.Final.jar:na]
    at org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:142) ~[netty-3.2.5.Final.jar:na]
    at org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:90) ~[netty-3.2.5.Final.jar:na]
    at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:282) ~[netty-3.2.5.Final.jar:na]
    ... 41 common frames omitted

2022-06-23 09:50:32.380  INFO 5052 --- [           main] f.a.ReferenceAnnotationBeanPostProcessor : class com.alibaba.dubbo.config.spring.beans.factory.annotation.ReferenceAnnotationBeanPostProcessor was destroying!
Disconnected from the target VM, address: '127.0.0.1:61810', transport: 'socket'

但是我将yaml文件修改为properties文件后,服务可以正常启动
properties文件的配置:

img

服务提供者的使用的dubbo依赖为0.1.0,是什么原因导致yaml配置文件不生效,但是properties文件可以生效?

  • 写回答

1条回答 默认 最新

  • 丶未来 2022-06-23 14:32
    关注

    是不是在配置中心配置了 启动的时候去配置中心拉取配置文件不用本地配置文件

    评论

报告相同问题?

问题事件

  • 创建了问题 6月23日

悬赏问题

  • ¥15 我这模型写的不对吗?为什么lingo解出来的下面影子价格这一溜少一个变量
  • ¥50 树莓派安卓APK系统签名
  • ¥15 maple软件,用solve求反函数出现rootof,怎么办?
  • ¥65 汇编语言除法溢出问题
  • ¥15 Visual Studio问题
  • ¥20 求一个html代码,有偿
  • ¥100 关于使用MATLAB中copularnd函数的问题
  • ¥20 在虚拟机的pycharm上
  • ¥15 jupyterthemes 设置完毕后没有效果
  • ¥15 matlab图像高斯低通滤波