Wildfly 9.x startet with errors: address already in use

Question

Wildfly 9.x startet with errors: address already in use

I am new to Eclipse, JSF, Wildfly and so on. I get this stack:

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)

How can I solve this problem?

There are several connections on port 80. Do I need to check all the ip addresses with whois to identify an application on my computer that already uses port 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

This error is always present, also if I restart the computer.

Edit:

 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

+8

eclipse java-ee wildfly

cy221 Aug 14 '15 at 20:14

source share

4 answers

Ualter jr. · Answer 1 · 2016-02-13T00:15:58+0000

Check if you have a service called NVIDIA Network Service running on your computer.

By the way, this NVIDIA service runs on port 9990 , which is used for the Wildfly admin console.

In my case, it was only stopping this service and rebooting the Wildfly server.

Rigre Garciandía · Answer 2 · 2015-08-16T07:44:52+0000

WildFly is trying to use a port on your PC that is already in use. Check your logs: " Caused: java.net.BindException : Already Existing Address: bind "

Check if WildFly uses the port, and then you can check if this port is used for any other application, it can be another instance of WildFly, but it can be any other application. For example, port 80 could be apache / IIS or any other web server running on your PC.

Typically, WildFly (and JBOSS) uses 8080 by default and looks like you are listening to an application on this port, and WildFly uses several ports for other protocols and controls that need an application server. Using the netstat command, you can verify that another application is using these ports, for example (for port 8080) you can use the command:

netstat -aon | findstr: 8080

If you want to perform a quick test, you can pass this parameter to WildFly " -Djboss.socket.binding.port-offset = 2000 ", this will increase all JBOSS / WildFly ports using 2000 (or any other value), for example, if your WildFly worked in " localhost: 8080 / your-context ", now it will be " localhost: 10080 / your-context ".

If your JBOSS / WildFly runs on port 80 , you can play with this parameter for testing with another port, for example, " -Djboss.socket.binding.port-offset = 10000 " you will also get port 10080 .

Good luck;)

teacurran · Answer 3 · 2015-08-15T08:11:51+0000

Wildfly already works when you try to run it. Check your process viewer, it can be displayed as a wildfly, which can be displayed just like "java".

You can start it as a service, you can start it from the command line, it is possible that Eclipse has started it and no longer knows about it.

Andreas Dietrich · Answer 4 · 2017-06-28T20:04:07+0000

Just checking my (default) port in the browser via http: // localhost: 8080 , it was obvious that it was a service / application that I installed / tested under the name Intrexx (by the way, it uses the Tomcat application server). After uninstallation, everything was fine.

Wildfly 9.x startet with errors: address already in use

More articles: