Description of problem:
This BZ was found while verifying these BZs: BZ 1119240, BZ 1016678. In the environment with domain controller running on one machine and host controller running on another, if the host controller is started using default host-slave.xml file, it appears as down in JON web ui, as it does not have http-interface configured. The BZs above were fixed in a way that the user is clearly informed that http-interface should be enabled and the port should be specified in connection settings.

However, after enabling http-interface and setting the port, the host controller stays down and the following exception is logged in agent.log:

java.lang.Exception: Failed to read attribute [process-type] of address [] - response: Result{outcome='failed', failureDescription=JBAS015135: The security realm is not ready to process requests, see http://127.0.0.1:9990/error/index.html, rolledBack=true}
	at org.rhq.modules.plugins.jbossas7.BaseComponent.readAttribute(BaseComponent.java:894)
	at org.rhq.modules.plugins.jbossas7.BaseComponent.readAttribute(BaseComponent.java:878)
	at org.rhq.modules.plugins.jbossas7.BaseComponent.readAttribute(BaseComponent.java:870)
	at org.rhq.modules.plugins.jbossas7.HostControllerComponent.getProcessTypeAttrValue(HostControllerComponent.java:375)
	at org.rhq.modules.plugins.jbossas7.HostControllerComponent.start(HostControllerComponent.java:88)
	at sun.reflect.GeneratedMethodAccessor46.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:759)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	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)

Version-Release number of selected component (if applicable):
Version:3.3.0.ER02
Build Number:4fbb183:7da54e2

How reproducible:
always

Steps to Reproduce:
1. Start EAP 6 DC using host-master.xml on one machine and EAP 6 HC using host-slave.xml on another machine.
2. Inventory both EAPs and notice that HC is unavailable.
3. Stop the HC.
4. Edit HC's host-slave.xml and add http-interface tag:
*********************************************
...
<management-interfaces>
    <native-interface security-realm="ManagementRealm">
        <socket interface="management" port="${jboss.management.native.port:9999}"/>
    </native-interface>
    <http-interface security-realm="ManagementRealm">
        <socket interface="management" port="${jboss.management.http.port:9990}"/>
    </http-interface> 
</management-interfaces>
...
*********************************************
5. In web UI edit HC's connection settings: Port = 9990
6. Start HC (using host-slave.xml)


Actual results:
HC stays down and the exception (see above) is logged in agent.log.


Expected results:
HC is up and no exception is logged.


Additional info:
See also BZ 1119240, BZ 1016678.