connections java.net.BindException: Address already in use_解决方案

一、问题描述

在Linux服务器(CentOS7系统)中配置并启动JMeter远程监控服务器资源所需的ServerAgent目录下的 startAgent.sh 文件时,系统出现异常提示,如

[[email protected] ServerAgent-2.2.3]# ./startAgent.sh
INFO    2018-12-15 10:29:17.634 [kg.apc.p] (): Binding UDP to 4444
ERROR   2018-12-15 10:29:17.686 [kg.apc.p] (): Can‘t accept UDP connections
java.net.BindException: Address already in use
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.DatagramChannelImpl.bind(DatagramChannelImpl.java:691)
        at sun.nio.ch.DatagramSocketAdaptor.bind(DatagramSocketAdaptor.java:91)
        at kg.apc.perfmon.PerfMonWorker.listenUDP(PerfMonWorker.java:144)
        at kg.apc.perfmon.PerfMonWorker.startAcceptingCommands(PerfMonWorker.java:107)
        at kg.apc.perfmon.AgentTool.processParams(AgentTool.java:72)
        at kg.apc.cmdtools.PluginsCMD.processParams(PluginsCMD.java:63)
        at kg.apc.cmdtools.PluginsCMD.processParams(PluginsCMD.java:23)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

二、问题分析

从以上抛出的异常信息中提取关键的提示信息:
"Can‘t accept UDP connections
java.net.BindException: Address already in use"

分析:ServerAgent默认开始的是4444端口,提示“不能接收UDP连接,地址已在使用中”,很可能是该端口已被占用,需要修改为新的端口号再启用or先暂停该端口对应的进程,然后再启用ServerAgent服务

三、解决方案

方式1:先暂停4444端口,再启用ServerAgent服务

查询4444端口当前对应的进程:lsof -i:4444

[[email protected] ServerAgent-2.2.3]# lsof -i:4444
COMMAND    PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
java    104069 root   18u  IPv6 3997358      0t0  UDP *:krb524
java    104069 root   19u  IPv6 3997549      0t0  TCP *:krb524 (LISTEN)

关闭指定PID号码的进程(4444端口进程):kill -9 104069
此时,亦可正常启用ServerAgent服务,如下:

[[email protected] ServerAgent-2.2.3]# kill -9 104069
[[email protected] ServerAgent-2.2.3]# lsof -i:4444
[[email protected] ServerAgent-2.2.3]# ./startAgent.sh
INFO    2018-12-15 10:41:51.043 [kg.apc.p] (): Binding UDP to 4444
INFO    2018-12-15 10:41:52.059 [kg.apc.p] (): Binding TCP to 4444
INFO    2018-12-15 10:41:52.066 [kg.apc.p] (): [email protected] Agent v2.2.3 started
方式2:修改ServerAgent端口,再启用ServerAgent服务

./startAgent.sh –udp-port 0 –tcp-port xxxx ("xxxx" 为新端口号,如:4567)
./startAgent.sh –udp-port 0 –tcp-port 4567

原文地址:https://www.cnblogs.com/insane-Mr-Li/p/10929952.html

时间: 2024-07-30 04:25:08

connections java.net.BindException: Address already in use_解决方案的相关文章

java.net.BindException: Address already in use: JVM_Bind <null>:8080错误

今天打开myeclipse出现java.net.BindException: Address already in use: JVM_Bind <null>:8080错误 从网上搜了一下大多是讲端口被占用 用netstat -ano 查看8080端口,根据PID结束对应的进程. 表示很无语,我用命令查看8080端口没有被占用,下面是我搜索的另外的解决方法,我的能够成功解决. 在tomcat--->bin/startup.bat 编辑 添加java的环境就可以了: set JAVA_HOM

端口占用的一种形式 Failed to initialize end point associated with ProtocolHandler [&quot;ajp-bio-8090&quot;] java.net.BindException: Address already in use: JVM_Bind &lt;null&gt;:8090

严重: Failed to initialize end point associated with ProtocolHandler ["ajp-bio-8090"]java.net.BindException: Address already in use: JVM_Bind <null>:8090 at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:413) at org.apache.tomc

- Exception follows. org.apache.flume.FlumeException: java.net.BindException: Address already in use

[ERROR - org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:251)] Unable to start EventDrivenSourceRunner: { source:org.apache.flume.source.NetcatSource{name:s1,state:IDLE} } - Exception follows. org.apache.fl

怎么处理java.net.BindException: Address already in use: JVM_Bind

1出现java.net.BindException: Address already in use: JVM_Bind的原因是因为你所使用的端口被使用了,所以我们可以查看谁在用,然后关掉就行了,下面我来演示一下过程: 我的tomcat中8080端口被占用了,win+R输入cmd进入命令行,输入netstat -ano命令,如图所示 我们从本地地址可以看到8080端口被PID为5456占用,所以就打开任务管理器,查看--选择列-勾选PID,找到5456结束进程,一切OK!!

(解决tomcat端口被占用的问题)create[8005]java.net.BindException: Address already in use: JVM_Bind

create[8005]java.net.BindException: Address already in use: JVM_Bind”,原来是Tomcat8005端口被其他进程占用,8005端口是用来关闭TOMCAT服务的端口,解决的方法如下 1.方法一,修改tomcat/conf/server.xml文件 打开server.xml 将<Server port="8005" shutdown="SHUTDOWN">中8005改成不常用的端口号即可,比

Tomcate 启动异常,java.net.BindException: Address already in use: JVM_Bind:80的解决办法

一直用Tomcat,但是前几天突然报错:           java.net.BindException: Address already in use: JVM_Bind:80 第一反应就是80端口被占用了. 解决方案: 1.先用命令 netstat -ano 看一下各个端口(Local Address 列的端口号)占用和进程PID. 查看后发现我本地的8080端口被进程PID13888占用 2.然后在任务管理器里,查看进程,找到PID为13888的进程然后结束它(我的13888进程已经结束

严重: StandardServer.await: create[localhost:8005]: java.net.BindException: Address already in use: JVM_Bind

错误描述:严重: StandardServer.await: create[localhost:8005]: java.net.BindException: Address already in use: JVM_Bind 解决方法:这是端口号被占用,先查看端口号是被谁占用的,我的第一次查找到的是Tomcat7.0,kill掉进程,重新打开eclipse启动tomcat,发现还是同样的错: 又使用同样的方法,发现是java.exe占用,然后kill掉,发现Tomcat可启动. ---------

Unable to open debugger port (127.0.0.1:63777): java.net.BindException &quot;Address already in use: JVM

对Intellij IDEA是又爱又恨呀,爱的比myeclipse用起来爽手多了,恨的是刚开始用还不是很习惯. 偶尔启动Debug模式用Tomcat来调试会报以下错误: Unable to open debugger port (127.0.0.1:63777): java.net.BindException "Address already in use: JVM_Bind" 困扰了我好久,试过删掉taget文件夹rebuild,试过杀掉java进程和重启机器,但是就是没效果. 今天

jmeter 运行脚本报错 java.net.BindException: Address already in use

在win下跑jmeter时,在聚合报告中出现错误.打开日志文件(前提是将日志写入了指定文件) 发现报错的原因为:java.net.BindException: Address already in use: connect 该问题的原因为: Windows XP提供给 TCP/IP链接的端口为 1024-5000,并且要四分钟来循环回收他们.就导致我们在短时间内跑大量的请求时将端口占满了.   解决方案为: 1.cmd中,用regedit命令打开注册表 2.在 HKEY_LOCAL_MACHIN