JBoss ON Agent throws " Invalid port: 0" error while trying to discover EAP
Issue
-
Host Controller not discovered and the following is logged in the
agent.logfile:ERROR [ResourceDiscoveryComponent.invoker.daemon-216] (rhq.modules.plugins.jbossas7.HostControllerDiscovery)- Discovery of a JBossAS7 Host Controller Resource failed for process: pid=[14555], name=[java], ppid=[14538]. java.lang.IllegalArgumentException: Invalid port: 0 ... -
Metrics schedules for datasource resource in EAP server - in domain mode show only Availability
- JBoss ON is having issues showing the status of the JBoss EAP Host Controller
- When I look at the inventory of the specific server, the EAP domain slave does not appear, nor does the Application server specified for that slave
-
JBoss ON reports:
org.rhq.core.pluginapi.inventory.InvalidPluginConfigurationException: Failed to start component for Resource[id=10123, uuid=03139897-4a4c-4e07-92c9-231f4842f8fb, type={JBossAS7}JBossAS7 Host Controller, key=hostConfig: /opt/jboss/jboss-eap-6.3/web/domain/configuration/web-slave.xml, name=EAP Host Controller (myHost localhost:0), parent=myHost.example.com, version=EAP 6.3.2.GA] - Unable to detect management port. Please enable management HTTP interface on and then set correct port number in Connection Settings of this resource ...
Environment
- Red Hat JBoss Operations Network (ON) 3.1, 3.2 1, 3.3
- Red Hat JBoss Enterprise Application Platform (EAP) 6, 7
- EAP running in
domainmode - Two or more host controllers in the same domain
- Host Controller started using
host-slave.xmlconfiguration file - Affected host controller missing from the inventory
-
For JBoss ON 3.2 review knowledge solution: 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 if the host controller is already in the inventory ↩︎
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
