WildFly 8.x, "java.net.BindException: Address already in use" on fresh install in windows Vista/7/8

Version 1

    I had some problems recently starting the newly installed WIldFly 8 server. On the very first launch it gave me the java.net.BindException rendering the server inoperable.

     

    The whole log looked like this:

    11:54:32,158 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
    11:54:32,378 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.0.Final
    11:54:32,438 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.0.0.Final "WildFly" starting
    11:54:33,218 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
    11:54:33,239 INFO  [org.xnio] (MSC service thread 1-6) XNIO version 3.2.0.Final
    11:54:33,239 INFO  [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.2.0.Final
    11:54:33,269 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem.
    11:54:33,269 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 50) JBAS015537: Activating WebServices Extension
    11:54:33,269 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 46) JBAS013171: Activating Security Subsystem
    11:54:33,269 INFO  [org.jboss.as.security] (MSC service thread 1-14) JBAS013170: Current PicketBox version=4.0.20.Final
    11:54:33,279 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 41) JBAS011800: Activating Naming Subsystem
    11:54:33,289 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 39) JBAS012615: Activated the following JSF Implementations: [main]
    11:54:33,299 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.3.Final)
    11:54:33,319 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 49) JBAS017502: Undertow 1.0.0.Final starting
    11:54:33,319 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-14) JBAS017502: Undertow 1.0.0.Final starting
    11:54:33,339 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
    11:54:33,339 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010417: Started Driver service with driver-name = h2
    11:54:33,349 INFO  [org.jboss.as.naming] (MSC service thread 1-5) JBAS011802: Starting Naming Service
    11:54:33,349 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
    11:54:33,399 INFO  [org.jboss.remoting] (MSC service thread 1-12) JBoss Remoting version 4.0.0.Final
    11:54:33,409 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 49) JBAS017527: Creating file handler for path D:\_code\_servers\wildfly-8.0.0.Final/welcome-content
    11:54:33,439 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-16) JBAS017525: Started server default-server.
    11:54:33,452 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-13) JBAS017531: Host default-host starting
    11:54:33,563 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
    11:54:33,619 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory D:\_code\_servers\wildfly-8.0.0.Final\standalone\deployments
    11:54:33,649 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-12) MSC000001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: JBAS015811: Failed to start the http-interface service
        at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:258) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
        at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
    Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind
        at org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:156) [wildfly-domain-http-interface-8.0.0.Final.jar:8.0.0.Final]
        at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:224) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
        ... 5 more
    Caused by: java.net.BindException: Address already in use: bind
        at sun.nio.ch.Net.bind0(Native Method) [rt.jar:1.7.0_45]
        at sun.nio.ch.Net.bind(Net.java:444) [rt.jar:1.7.0_45]
        at sun.nio.ch.Net.bind(Net.java:436) [rt.jar:1.7.0_45]
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214) [rt.jar:1.7.0_45]
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) [rt.jar:1.7.0_45]
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67) [rt.jar:1.7.0_45]
        at org.xnio.nio.NioXnioWorker.createTcpConnectionServer(NioXnioWorker.java:175)
        at org.xnio.XnioWorker.createStreamConnectionServer(XnioWorker.java:242) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
        at org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:135) [wildfly-domain-http-interface-8.0.0.Final.jar:8.0.0.Final]
        ... 6 more
    
    11:54:33,679 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-10) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
    11:54:33,789 INFO  [org.jboss.ws.common.management] (MSC service thread 1-13) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.3.Final
    11:54:33,789 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
        ("core-service" => "management"),
        ("management-interface" => "http-interface")
    ]) - failure description: {"JBAS014671: Failed services" => {"jboss.serverManagement.controller.management.http" => "org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: JBAS015811: 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"}}
    11:54:33,829 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
    JBAS014777:   Services which failed to start:      service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: JBAS015811: Failed to start the http-interface service
    
    11:54:33,839 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015964: Http management interface is not enabled
    11:54:33,839 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
    11:54:33,839 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.0.0.Final "WildFly" started (with errors) in 1911ms - Started 178 of 230 services (1 services failed or missing dependencies, 80 services are lazy, passive or on-demand)
    
    
    

     

    Those having the same problem should check who else uses the port 9990 in your Windows system. TCPView is a good tool to find out the guilty of charge. One of possible common causes in this case is NVIDIA Network Service (NvNetworkService.exe). If that's the case just find it in your Windows services list and stop/disable it. The service itself is responsible for checking for Nvidia drivers updates, so any time you want it back just turn it on manually.

     

    Hope this helps and Regards