Created attachment 803494 [details] modified config files Description of problem: JON unable to discover EAP servers when EAP domain mode is started from external folders Version-Release number of selected component (if applicable): EAP 6.1.1 JON 3.1.2 and associated agent and plugins How reproducible: Steps to Reproduce: 1. Make copies of <EAP-home>/domain folder as machine1, machine2 and machine3 2. make appropraite changes to domain, host-master.xml and host-slave.xml files in machine1, 2, 3 folders (see attachement) to simulate machine 1- domain controller machine 2 - server-one and server-two (EAP servers) machine 3 - server-three 3. start servers ./domain.sh --host-config=host-master.xml -Djboss.domain.base.dir=/machine1/ ./domain.sh -Djboss.domain.base.dir=/machine2/ --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 ./domain.sh -Djboss.domain.base.dir=/machine3/ --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 Actual results: JON did discovered domain controller but not teh EAP servers. "managed servers" folder was missing Expected results: However when I start EAP in domain mode with out of the box setting. JON worked fine and dsicovered all the EAP servers Additional info:
This appears to be the same/duplicate of bug 969621. An agent debug log would be required to confirm.
Sudheer, I've tried out your config files. It didn't work for me. Your config files for slave host controllers did not define http management interfaces, thatswhy agent was not able to talk to machine2 and 3 controllers at all. In my case, agent discovered host controllers and detected port 0 (Which is Bug 1016678) Please add (for machine2) <http-interface security-realm="ManagementRealm"> <socket interface="management" port="${jboss.management.http.port:29990}"/> </http-interface> under "management-interfaces" element. after changing host-slave.xml files like mentioned above managed servers are correctly discovered. verified on JON 3.2.0.ER3