Adding http-interface in the host controller's host-slave.xml is not recognised by JBoss ON Agent causing Host Controller's availability to stay DOWN

Issue

• I have changed the management interface in the file host-slave.xml as per knowledge solution: JBoss ON Agent throws " Invalid port: 0" error while trying to discover EAP 6, restarted the jboss eap server and the agent but I still get the same error;

• JBoss ON has discovered my Host Controller but it is marked as DOWN and the following WARN is logged in the agent.log file:

2014-07-11 10:23:40,185 WARN  [InventoryManager.availability-1] (rhq.core.pc.inventory.AvailabilityExecutor)- Availability collection failed with exception on Resource[id=10103, uuid=5eec6ae0-5313-4dd7-8537-03eec96b9800, type={JBossAS7}JBossAS7 Host Controller, key=hostConfig: /opt/myEAPserver/domain/configuration/host-slave.xml, name=EAP Host Controller (localhost:0), parent=myServer.com, version=EAP 6.2.0.GA], availability will be reported as DOWN
org.rhq.core.clientapi.agent.PluginContainerException: Failed to start component for resource Resource[id=10103, uuid=5eec6ae0-5313-4dd7-8537-03eec96b9800, type={JBossAS7}JBossAS7 Host Controller, key=hostConfig: /opt/myEAPserver/domain/configuration/host-slave.xml, name=EAP Host Controller (localhost:0), parent=myServer.com, version=EAP 6.2.0.GA].
        at org.rhq.core.pc.inventory.InventoryManager.activateResource(InventoryManager.java:1941)
        at org.rhq.core.pc.inventory.AvailabilityExecutor.checkInventory(AvailabilityExecutor.java:361)
        at org.rhq.core.pc.inventory.AvailabilityExecutor.checkInventory(AvailabilityExecutor.java:429)
        at org.rhq.core.pc.inventory.AvailabilityExecutor.startScan(AvailabilityExecutor.java:195)
        at org.rhq.core.pc.inventory.AvailabilityExecutor.call(AvailabilityExecutor.java:152)
        at org.rhq.core.pc.inventory.AvailabilityExecutor.run(AvailabilityExecutor.java:111)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.IllegalArgumentException: Invalid port: 0
        at org.rhq.modules.plugins.jbossas7.ASConnection.<init>(ASConnection.java:165)
        at org.rhq.modules.plugins.jbossas7.ASConnection.newInstanceForServerPluginConfiguration(ASConnection.java:230)
        at org.rhq.modules.plugins.jbossas7.BaseServerComponent.start(BaseServerComponent.java:98)
        at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocation.call(ResourceContainer.java:654)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)

• Adding http-interface in the host controller's host-slave.xml is not recognised by JBoss ON Agent causing Host Controller's availability to stay DOWN.