2 Replies Latest reply on Dec 27, 2015 7:55 AM by Wolfgang Mayer

    wildfly-10.0.0.CR5: bind.address is only working on 127.0.0.1

    Wolfgang Mayer Master

      I've realized a "strange" behaviour in wildfly-10.0.0.CR5.

      When I use the standard standalone-full.xml configuration the server starts up fine. But when I change eg the jboss.bind.address.management address to some other value the server logs messages like

       

      2015-12-26 11:56:56,073 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory

      2015-12-26 11:56:56,079 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("interface" => "management")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.network.management" => "org.jboss.msc.service.StartException in service jboss.network.management: WFLYSRV0082: failed to resolve interface management"}}

      2015-12-26 11:56:56,129 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report

      WFLYCTL0186:   Services which failed to start:      service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: WFLYSRV0082: failed to resolve interface management

       

      11:56:56,224 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.0.0.CR5 (WildFly Core 2.0.5.Final) started (with errors) in 4739ms - Started 298 of 605 services (4 services failed or missing dependencies, 401 services are lazy, passive or on-demand)

       

      The ping confirms that the address is OK.

       

      Do you have any idea where the problem might be?

        • 1. Re: wildfly-10.0.0.CR5: bind.address is only working on 127.0.0.1
          Jay SenSharma Master

          I have tested with WildFly 10 CR5  and i do not see the issue which you reported.  So it looks like there might be some issue at your Network interface configuration.

           

          I checked the following to test:

           

          I started my WildFly 10 CR5 as following:

           

          $ ./standalone.sh -Djboss.bind.address.management=168.252.85.132
          .
          .
          =======
          OUTPUT
          =======
          12:21:51,229 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://168.252.85.132:9990/management
          12:21:51,229 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://168.252.85.132:9990
          
          

           

           

          I verified if the above mentioned interface exist or not as following:

           

          $ ifconfig | grep 168.252.85.132
          
          

           

          So please check your problematic interface if it is listed in the "ifconfig" command output or not ?

           

           

          NOTE: If i enter a non existing interface/IP-Address then only i can see the error as following (So you will need to check your interface is correct or not) .  In the below case i intentionally entered an incorrect Interface detail "160.160.84.131" (non existing IP)

           

          ./standalone.sh -Djboss.bind.address.management=160.160.84.131
          .
          .
          12:27:16,178 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: WFLYSRV0082: failed to resolve interface management
            at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:91)
            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)
          

           

          Regards

          Jay SenSharma

          • 2. Re: wildfly-10.0.0.CR5: bind.address is only working on 127.0.0.1
            Wolfgang Mayer Master

            Sorry, my mistake. It is working now