Wildfly 9.x startet有错误:地址已在使用中
cy2*_*221 10 eclipse java-ee wildfly
我是Eclipse,JSF,Wildfly等的新手.我得到这个堆栈跟踪:
22:03:42,430 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service
at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:269)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind
at org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:160)
at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:235)
... 5 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:437)
at sun.nio.ch.Net.bind(Net.java:429)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
at org.xnio.nio.NioXnioWorker.createTcpConnectionServer(NioXnioWorker.java:182)
at org.xnio.XnioWorker.createStreamConnectionServer(XnioWorker.java:243)
at org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:147)
... 6 more
22:03:42,431 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
22:03:42,551 INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final
22:03:43,287 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 61) Mojarra 2.2.11-jbossorg-1 20150505-1501 für Kontext '/JSF Hello World' wird initialisiert.
22:03:43,721 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0021: Registered web context: /JSF Hello World
22:03:43,727 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("core-service" => "management"),
("management-interface" => "http-interface")
]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.serverManagement.controller.management.http" => "org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service
Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind
Caused by: java.net.BindException: Address already in use: bind"}}
22:03:43,758 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "JSF Hello World.war" (runtime-name : "JSF Hello World.war")
22:03:43,786 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service
22:03:43,884 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled
22:03:43,884 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled
22:03:43,884 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 12675ms - Started 270 of 455 services (2 services failed or missing dependencies, 221 services are lazy, passive or on-demand)
我该如何解决这个问题？
端口80上有一些连接.我是否必须使用whois检查所有ip地址,以便在我的计算机上识别已使用端口80的应用程序？
C:\Users\me7D-User>netstat -aon | findstr "80"
TCP 0.0.0.0:8092 0.0.0.0:0 ABHÖREN 4
TCP 127.0.0.1:8080 0.0.0.0:0 ABHÖREN 8868
TCP 127.0.0.1:8080 127.0.0.1:59241 HERGESTELLT 8868
TCP 127.0.0.1:59177 127.0.0.1:8080 WARTEND 0
TCP 127.0.0.1:59180 127.0.0.1:59181 HERGESTELLT 8868
TCP 127.0.0.1:59181 127.0.0.1:59180 HERGESTELLT 8868
TCP 127.0.0.1:59230 127.0.0.1:8080 WARTEND 0
TCP 127.0.0.1:59241 127.0.0.1:8080 HERGESTELLT 11024
TCP 192.168.0.100:59166 173.194.113.41:80 WARTEND 0
TCP 192.168.0.100:59249 104.16.102.85:80 HERGESTELLT 8392
TCP 192.168.0.100:59250 216.58.211.42:80 HERGESTELLT 8392
TCP 192.168.0.100:59252 103.31.7.34:80 HERGESTELLT 8392
TCP 192.168.0.100:59253 216.58.211.42:80 WARTEND 0
TCP 192.168.0.100:59254 190.93.247.58:80 HERGESTELLT 8392
TCP 192.168.0.100:59255 190.93.247.58:80 HERGESTELLT 8392
TCP 192.168.0.100:59256 190.93.247.58:80 WARTEND 0
TCP 192.168.0.100:59257 190.93.247.58:80 HERGESTELLT 8392
TCP 192.168.0.100:59258 190.93.247.58:80 HERGESTELLT 8392
TCP 192.168.0.100:59259 190.93.247.58:80 HERGESTELLT 8392
TCP 192.168.0.100:59264 104.16.12.8:80 HERGESTELLT 8392
TCP 192.168.0.100:59265 88.221.92.32:80 HERGESTELLT 8392
TCP 192.168.0.100:59266 88.221.92.176:80 HERGESTELLT 8392
TCP 192.168.0.100:59267 173.194.113.36:80 HERGESTELLT 8392
TCP 192.168.0.100:59268 104.16.12.8:80 WARTEND 0
TCP 192.168.0.100:59269 88.221.92.32:80 WARTEND 0
TCP 192.168.0.100:59270 88.221.92.176:80 WARTEND 0
TCP 192.168.0.100:59271 54.204.10.55:80 HERGESTELLT 8392
TCP 192.168.0.100:59272 54.204.10.55:80 WARTEND 0
TCP 192.168.0.100:59273 95.172.94.34:80 WARTEND 0
TCP 192.168.0.100:63749 216.34.181.97:80 SCHLIESSEN_WARTEN 1680
TCP 192.168.0.100:63812 216.34.181.97:80 SCHLIESSEN_WARTEN 1680
TCP [::]:8092 [::]:0 ABHÖREN 4
UDP 127.0.0.1:49880 *:* 3272
UDP [fe80::100:7f:fffe%11]:54045 *:* 49
56
UDP [fe80::5efe:192.168.0.100%15]:54045 *:*
4956
UDP [fe80::5efe:192.168.137.1%14]:54045 *:*
4956
UDP [fe80::a9:d477:68a9:2472%10]:1900 *:*
3364
UDP [fe80::a9:d477:68a9:2472%10]:54045 *:*
4956
UDP [fe80::a9:d477:68a9:2472%10]:56718 *:*
3364
UDP [fe80::3d9d:1f6f:e25:35b%13]:53 *:*
1292
UDP [fe80::3d9d:1f6f:e25:35b%13]:546 *:*
1100
UDP [fe80::3d9d:1f6f:e25:35b%13]:1900 *:*
3364
UDP [fe80::3d9d:1f6f:e25:35b%13]:54045 *:*
4956
UDP [fe80::3d9d:1f6f:e25:35b%13]:56719 *:*
3364
如果我重新启动计算机,则始终存在此错误.
编辑:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\me7D-User>netstat -aon | findstr "8080"
TCP 127.0.0.1:8080 0.0.0.0:0 ABHÖREN 7500
TCP 127.0.0.1:8080 127.0.0.1:60095 HERGESTELLT 7500
TCP 127.0.0.1:8080 127.0.0.1:60096 HERGESTELLT 7500
TCP 127.0.0.1:60035 127.0.0.1:8080 WARTEND 0
TCP 127.0.0.1:60095 127.0.0.1:8080 HERGESTELLT 11024
TCP 127.0.0.1:60096 127.0.0.1:8080 HERGESTELLT 11024
Ual*_*Jr. 53
检查您的计算机上是否有名为NVIDIA Network Service的服务.
巧合的是,这个NVIDIA服务正在9990端口运行,用于Wildfly的管理控制台.
就我而言,它只是停止此服务并重新启动Wildfly服务器.
小智 6
WildFly 正在尝试使用您 PC 中已在使用的端口。检查您的日志：“引起：java.net.BindException：地址已在使用：绑定”
检查 WildFly 正在使用的端口，然后您可以检查此端口是否正在用于任何其他应用程序，它可能是 WildFly 的另一个实例，但也可以是任何其他应用程序。例如，端口80可以是 apache/IIS 或在您的 PC 中运行的任何其他 Web 服务器。
通常，WildFly（和 JBOSS）默认使用8080，看起来您有一个应用程序在此端口侦听，WildFly 还使用更多端口用于应用程序服务器需要的其他协议和管理。使用命令 netstat 您可以检查其他应用程序正在使用这些端口，例如（对于 8080 端口）您可以使用以下命令：
netstat -aon | findstr :8080
如果你想做一个快速测试，你可以将此参数传递给 WildFly “ -Djboss.socket.binding.port-offset=2000 ” 这将使 JBOSS/WildFly 使用的所有端口增加 2000（或任何其他值），然后为例如，如果您的 WildFly 在“ localhost:8080/your-context ”中运行，现在将是“ localhost:10080/your-context ”。
如果您的 JBOSS/WildFly 运行在80端口，您也可以使用此参数来测试另一个端口，例如“ -Djboss.socket.binding.port-offset=10000 ”也会为您带来10080端口。
祝你好运 ;）
当您尝试启动 Wildfly 时，它已经在运行。检查您的进程查看器，它可能显示为 Wildfly，也可能显示为“java”。
您可以将其作为服务运行，也可以从命令行运行它，Eclipse 可能启动了它并且不再意识到它。
| 归档时间： |
|
| 查看次数： |
22958 次 |
| 最近记录： |