【Address already in use: bind】

已于 2022-02-16 14:21:44 修改
阅读量1k 收藏
点赞数
文章标签： zookeeper java spring
于 2022-02-16 14:09:44 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/Ahull/article/details/122959751
版权

报错信息：

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.alibaba.dubbo.spring.boot.DubboProviderAutoConfiguration': Invocation of init method failed; nested exception is com.alibaba.dubbo.rpc.RpcException: Fail to start server(url: dubbo://192.168.254.1:20880/com.hpower.springboot.service.StudentService?anyhost=true&application=h024-spb-dubbo-ssm-provider&bind.ip=192.168.254.1&bind.port=20880&channel.readonly.sent=true&codec=dubbo&dubbo=2.6.0&generic=false&heartbeat=60000&interface=com.hpower.springboot.service.StudentService&methods=queryStudentById&pid=16916&side=provider&timeout=15000&timestamp=1644981716353) Failed to bind NettyServer on /192.168.254.1:20880, cause: Failed to bind to: /0.0.0.0:20880
	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:160) ~[spring-beans-5.3.15.jar:5.3.15]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:440) ~[spring-beans-5.3.15.jar:5.3.15]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1796) ~[spring-beans-5.3.15.jar:5.3.15]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:620) ~[spring-beans-5.3.15.jar:5.3.15]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542) ~[spring-beans-5.3.15.jar:5.3.15]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335) ~[spring-beans-5.3.15.jar:5.3.15]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-5.3.15.jar:5.3.15]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333) ~[spring-beans-5.3.15.jar:5.3.15]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208) ~[spring-beans-5.3.15.jar:5.3.15]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:953) ~[spring-beans-5.3.15.jar:5.3.15]
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918) ~[spring-context-5.3.15.jar:5.3.15]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583) ~[spring-context-5.3.15.jar:5.3.15]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145) ~[spring-boot-2.6.3.jar:2.6.3]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:732) [spring-boot-2.6.3.jar:2.6.3]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:414) [spring-boot-2.6.3.jar:2.6.3]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:302) [spring-boot-2.6.3.jar:2.6.3]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1303) [spring-boot-2.6.3.jar:2.6.3]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1292) [spring-boot-2.6.3.jar:2.6.3]
	at com.hpower.springboot.H024SpbDubboSsmProviderApplication.main(H024SpbDubboSsmProviderApplication.java:14) [classes/:na]
Caused by: com.alibaba.dubbo.rpc.RpcException: Fail to start server(url: dubbo://192.168.254.1:20880/com.hpower.springboot.service.StudentService?anyhost=true&application=h024-spb-dubbo-ssm-provider&bind.ip=192.168.254.1&bind.port=20880&channel.readonly.sent=true&codec=dubbo&dubbo=2.6.0&generic=false&heartbeat=60000&interface=com.hpower.springboot.service.StudentService&methods=queryStudentById&pid=16916&side=provider&timeout=15000&timestamp=1644981716353) Failed to bind NettyServer on /192.168.254.1:20880, cause: Failed to bind to: /0.0.0.0:20880
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:277) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.openServer(DubboProtocol.java:254) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.export(DubboProtocol.java:241) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:93) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:68) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.rpc.Protocol$Adaptive.export(Protocol$Adaptive.java) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.registry.integration.RegistryProtocol.doLocalExport(RegistryProtocol.java:181) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.registry.integration.RegistryProtocol.export(RegistryProtocol.java:121) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:91) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:66) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.rpc.Protocol$Adaptive.export(Protocol$Adaptive.java) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.config.ServiceConfig.doExportUrlsFor1Protocol(ServiceConfig.java:505) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:357) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:316) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.config.ServiceConfig.export(ServiceConfig.java:215) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.spring.boot.DubboProviderAutoConfiguration.initProviderBean(DubboProviderAutoConfiguration.java:84) ~[dubbo-spring-boot-starter-2.0.0.jar:na]
	at com.alibaba.dubbo.spring.boot.DubboProviderAutoConfiguration.init(DubboProviderAutoConfiguration.java:45) ~[dubbo-spring-boot-starter-2.0.0.jar:na]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_311]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_311]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_311]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_311]
	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:389) ~[spring-beans-5.3.15.jar:5.3.15]
	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:333) ~[spring-beans-5.3.15.jar:5.3.15]
	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:157) ~[spring-beans-5.3.15.jar:5.3.15]
	... 18 common frames omitted
Caused by: com.alibaba.dubbo.remoting.RemotingException: Failed to bind NettyServer on /192.168.254.1:20880, cause: Failed to bind to: /0.0.0.0:20880
	at com.alibaba.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:68) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.remoting.transport.netty.NettyServer.<init>(NettyServer.java:61) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.remoting.transport.netty.NettyTransporter.bind(NettyTransporter.java:31) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.remoting.Transporter$Adaptive.bind(Transporter$Adaptive.java) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.remoting.Transporters.bind(Transporters.java:56) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchanger.bind(HeaderExchanger.java:42) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.remoting.exchange.Exchangers.bind(Exchangers.java:70) ~[dubbo-2.6.0.jar:2.6.0]
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:275) ~[dubbo-2.6.0.jar:2.6.0]
	... 41 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.6.0.jar:2.6.0]
	at com.alibaba.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:63) ~[dubbo-2.6.0.jar:2.6.0]
	... 48 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_311]
	at sun.nio.ch.Net.bind(Net.java:438) ~[na:1.8.0_311]
	at sun.nio.ch.Net.bind(Net.java:430) ~[na:1.8.0_311]
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:225) ~[na:1.8.0_311]
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) ~[na:1.8.0_311]
	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]
	... 50 common frames omitted

报错如上，还是老问题，端口被占用了
zookeeper一般默认为2181 端口
win+r----->cmd----->执行 netstat -ano | findstr 2181 命令
查看2181端口是否已经被占用
ps:冒号后边的为端口号，找到最右列的数字（PID），打开任务管理器---->任务详情在这里插入图片描述
如图，然后将相应的PID结束任务即可

Ahull
关注
【异常】Caused by: java.net.BindException: Address already in use: bind
本本本添哥
02-11 2869
这个报错是因为端口号已经被占用了。两种解决方式：换端口号或者杀掉这个进程。
xxl-job 启动 java.net.BindException: Address already in use: bind
隔壁老瓦的专栏
11-08 1138
/** * xxl-job config * * @author xuxueli 2017-04-28 */ @Configuration public class XxlJobConfig { private Logger logger = LoggerFactory.getLogger(XxlJobConfig.class); @Value("${xxl.job.admin.addresses}") private String adminAddresses; .
java.net.BindException: Address already in use: bind
dianchaozong3657的博客
08-08 202
环境：jxse-2.7, netty-3.6.6.Final　　 现象：每次执行都抛出以下异常 八月 08, 2013 8:45:19 下午 net.jxta.logging.Logging logCheckedInfoINFO: Line 127 net.jxta.impl.endpoint.netty.NettyTransportServer.bindServerChannel(...
查Windows的端口及对应的服务 Address already in use: bind
IT大神帅杰的博客
03-31 538
Caused by: java.net.BindException: Address already in use: bind
Netty报java.net.BindException: Address already in use: bind
billluffy的博客
12-15 7623
1.错误提示：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.c
端口被占用(Address already in use: bind)
zxy13826134783的博客
09-09 676
本文转自：https://www.cnblogs.com/1012hq/p/11141855.html 当eclipse卡住了，然后强行关闭，再次打开运行时，会报Address already in use: bind，如下图： 当你知道对于的端口时，可以使用下面的方法进行解决，其它软件有类似问题也相似 1 打开cmd命令行，执行命令netstat -ano|findstr "8089"查看8089端口是否被占用及占用此端口的PID，从下图中可以看到占用端口的进程ID(PID)为.
PyCharm 2020.1启动报错 Caused by: java.net.BindException: Address already in use: bind
u013364850的专栏
03-17 3743
PyCharm 2020.1启动不了，报错信息如下 Internal error. Please refer to http://jb.gg/ide/critical-startup-errors java.util.concurrent.CompletionException: java.net.BindException: Address already in use: bind at java.base/java.util.concurrent.CompletableFuture.enco..
LifecycleException: Protocol handler start failed & BindException: Address already in use: bind
123
04-14 302
IDEA控制台异常图 2020-04-14 15:59:16.715 INFO 19936 --- [ main] o.apache.catalina.core.StandardService : Stopping service [Tomcat] 2020-04-14 15:59:16.722 WARN 19936 --- [ main] o.a...
Caused by: java.net.BindException: Address already in use: bind错误解决
抛弃幻想，准备斗争
03-18 2万+
此异常为springboot启动异常，tomcat端口已经启动了，占用了，把后台tomcat关闭即可： 在cmd命令窗口： 1.输入netstat -ano|findstr 8005，回车，显示在最后面的数字就是我们tomcat进程的端口号。 2.输入 taskkill /pid xxxx /f xxxx就是我们的端口号，回车，终止！ 终止不了：则输入tasklist | fin...
报错：Address already in use：bind （error while binding on 0.0.0.0/0.0.0.0:10603）
yogima的博客
07-10 2776
百度了一下大多是认为端口被占用，删掉进程中的javaw.exe即可，但我这边并没有这个进程。 最奇怪的是，平常有用的重启大法都失效了 原因： 这个项目在tomcat的server.xml中配了Context这一行 <host> …… <Context docBase="" path=""/> </host> 这个配置中docBase为项目具体路径，path...
启动程序端口被占用Address already in use: bind解决方案
热门推荐
yels303的专栏
03-15 3万+
例如我们web服务器8080端口被占用：Address already in use: bind 有两种解决方案：1、把占用8080端口的程序终止掉。2、修改tomcat配置文件里的默认端口号 1、关闭占用8080端口的程序 在windows下，用命令行：netstat -ano来显示协议统计信息和TCP/IP网络连接 找到占用8080端口 我们找到占用端口号80
Caused by: java.net.BindException: Address already in use: bind
橙子wj的博客
04-03 8345
项目中有若干微服务，挨个启动的时候，报错com.alibaba.dubbo.rpc.RpcException: Fail to start server(url: dubbo://10.118.44.10:20860/com.sf.sfpp.download.service.DownloadService?anyhost=true&application=sfpp&channel.readonly.
Address already in use: bind【解决办法】
最新发布
qq_37054954的博客
02-22 4081
端口号被占用
Dubbo Failed to bind NettyServer on /192.168.56.1:xx,cause:Address already in use:bind问题解决
旭东怪的博客
10-13 5515
问题描述： 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: ...
dubbo Failed to bind to: /0.0.0.0:20880 Address already in use 问题解决
王威振的博客
01-16 5870
如果tomcat启动，就会报这种错误。并且20880端口在启动前并没有被占用 在tomcat中 host标签增加 autoDeploy="false" deployOnStartup="false" deployOnStartup="false"：tomcat启动时，不部署webapps下的web所有应用 autoDeploy="false":避免两次部署相同的web应用程序...
springboot dubbo多模块中2个模块都既是提供者又是消费者，第二个启动会报错Address already in use: bind 20880，xml配置端口不是20880也会报这个错
a704397849的博客
07-01 2904
springboot dubbo多模块中2个模块都既是提供者又是消费者，第二个启动会报错Address already in use: bind 20880 错误的配置xml <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans" ...
记Dubbo服务启动异常[Address already in use]
liusf1993的博客
05-27 7975
最近在本地搭了个docker后,然后某个dubbo服务启动失败了,其他dubbo服务启动是正常的;看了下其他同事及测试环境,均运行正常;本地错误信息如下 com.alibaba.dubbo.rpc.RpcException: Fail to start server(url: dubbo://192.168.3.184:20880/ Failed to bind NettyServer on /...
Address already in use
nurture_的博客
12-17 616
造成的原因：已经启动的服务非正常关闭 例如：IDEA已经开启这个服务，但是由于卡死或其他，你没有关闭项目直接关闭了IDEA 解决： 我的报错信息是： Caused by: com.alibaba.dubbo.remoting.RemotingException: Failed to bind NettyServer on /10.0.130.167:20893, cause: Address already in use 第一步：打开终端（我的是mac笔记本）：直接输入 lsof -i:2
Failed to bind NettyServer on /192.168.**.*:20880, cause: Failed to bind to: /0.0.0.0:20880
好好学java
04-20 6336
一、概述 今天遇到的Dubbo的问题，做项目的时候，在做Dubbo的多个模块调用dubbo服务的时候遇到的问题，下面是这个问题和解决方案 二、问题异常消息 Failed to bind NettyServer on /192.168.128.1:20880, cause: Failed to bind to: /0.0.0.0:20880 at com.ali...
Address already in use: bind
04-03
The error message "Address already in use: bind" usually occurs when you're trying to start a server or a service that is already running or a process that is using the same port. One common ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值