Dubbo服务启动时Caused by: com.alibaba.dubbo.remoting.RemotingException: Failed to bind NettyServer on /19

小灰灰 2021-09-26 21:52 984阅读 0赞

严重: Exception sending context initialized event to listener instance of class [org.springframework.web.context.ContextLoaderListener]  
    com.alibaba.dubbo.rpc.RpcException: Fail to start server(url: dubbo://192.168.1.170:20880/xxxxFailed to bind NettyServer on /192.168.1.170:20880, cause: Failed to bind to: /0.0.0.0:20880  
        at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:289)  
        at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.openServer(DubboProtocol.java:266)  
        at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.export(DubboProtocol.java:253)  
        at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:55)  
        at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:56)  
        at com.alibaba.dubbo.rpc.Protocol$Adpative.export(Protocol$Adpative.java)  
        at com.alibaba.dubbo.registry.integration.RegistryProtocol.doLocalExport(RegistryProtocol.java:153)  
        at com.alibaba.dubbo.registry.integration.RegistryProtocol.export(RegistryProtocol.java:107)  
        at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:53)  
        at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:54)  
        at com.alibaba.dubbo.rpc.Protocol$Adpative.export(Protocol$Adpative.java)  
        at com.alibaba.dubbo.config.ServiceConfig.doExportUrlsFor1Protocol(ServiceConfig.java:485)  
        at com.alibaba.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:281)  
        at com.alibaba.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:242)  
        at com.alibaba.dubbo.config.ServiceConfig.export(ServiceConfig.java:143)  
        at com.alibaba.dubbo.config.spring.ServiceBean.onApplicationEvent(ServiceBean.java:109)  
        at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:96)  
        at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)  
        at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:948)  
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482)  
        at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:389)  
        at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:294)  
        at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:112)  
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4745)  
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5207)  
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)  
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)  
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)  
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)  
        at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1144)  
        at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1878)  
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)  
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)  
        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)  
    Caused by: com.alibaba.dubbo.remoting.RemotingException: Failed to bind NettyServer on /192.168.1.170:20880, cause: Failed to bind to: /0.0.0.0:20880  
        at com.alibaba.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:72)  
        at com.alibaba.dubbo.remoting.transport.netty.NettyServer.<init>(NettyServer.java:63)  
        at com.alibaba.dubbo.remoting.transport.netty.NettyTransporter.bind(NettyTransporter.java:33)  
        at com.alibaba.dubbo.remoting.Transporter$Adpative.bind(Transporter$Adpative.java)  
        at com.alibaba.dubbo.remoting.Transporters.bind(Transporters.java:48)  
        at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchanger.bind(HeaderExchanger.java:41)  
        at com.alibaba.dubbo.remoting.exchange.Exchangers.bind(Exchangers.java:63)  
        at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:287)  
        ... 35 more  
    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)  
        at com.alibaba.dubbo.remoting.transport.netty.NettyServer.doOpen(NettyServer.java:94)  
        at com.alibaba.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:67)  
        ... 42 more  
    Caused by: java.net.BindException: Address already in use: bind  
        at sun.nio.ch.Net.bind0(Native Method)  
        at sun.nio.ch.Net.bind(Net.java:433)  
        at sun.nio.ch.Net.bind(Net.java:425)  
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)  
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)  
        at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind(NioServerSocketPipelineSink.java:148)  
        at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket(NioServerSocketPipelineSink.java:100)  
        at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:74)  
        at org.jboss.netty.channel.Channels.bind(Channels.java:468)  
        at org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:192)  
        at org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen(ServerBootstrap.java:348)  
        at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:176)  
        at org.jboss.netty.channel.socket.nio.NioServerSocketChannel.<init>(NioServerSocketChannel.java:85)  
        at org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:142)  
        at org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:90)  
        at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:282)  
        ... 44 more

安装完zookeeper后启动服务端报错如如上

错误信息很明显说了地址已经被占用，以为一般的tomcat默认设置了自动部署，需要修改tomcat的 server.xml 属性

我用的tomcat7，默认配置如下

\[html\]  [view plain][]   [copy][view plain]

1.  **<****Host** appBase="webapps" autoDeploy="true"  name="localhost" unpackWARs="true"**>**

修改为

\[html\]  [view plain][]   [copy][view plain]

1.  **<****Host** appBase="webapps" autoDeploy="false" deployOnStartup="false" name="localhost" unpackWARs="true"**>**

在启动就好了。

注意：如果是在eclipse中修改你项目栏左侧server离得server.xml ,开始我修改的是我安装tomcat的硬盘的文件，每次都会自动还原成默认

[view plain]: https://blog.csdn.net/keepd/article/details/77326837#