JBoss EAP 6.3 on CentOS 6.5 - "Failed to resolve interface management

[mjgusa]

Hi:

I've installed JBoss EAP 6.3 on CentOS 6.5 and am getting the error mentioned in the subject when trying to start.  As the jboss user, I am running the command

standalone.sh -b 192.168.1.200

I do the bind because I wish to see this server from another machine on my network, but I get the same error even without the -b option.

The relevant part of the error is as follows:

18:59:23,559 INFO  [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.10.GA-redhat-1
18:59:23,627 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version (unknown)
18:59:23,646 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management
  at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
  at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
  at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
  at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]

I've searched for help and from what I can tell I've mad ethe proper changes to the standalone.xml file with respect to replacing localhost with my IP.  I was surprised not to see a match here in the forum for this problem. 

Any help would be appreciated.

Thanks!

[mjgusa]

Solved (that problem).  Apparently the standalone.xml file can't have any blank lines in within the <server>  element and sub-elements.

Still can't access JBoss from another machine though, even with -b 0.0.0.0

[rafachies]

From the version 6 of EAP, you can bind your applications and the management console with different interfaces. The -b parameter is used to change the binding of your applications, so the management console keeps using the 127.0.0.1 interface. To change the management console binding, start EAP with the parameter -Djboss.bind.address.management=your.ip

[mjgusa]

Thanks Rafael.  That is what I am doing now, but my problem ended up being the XML file.  JBoss never got far enough to bind to anything.