JON is unable to manage or monitor EAP 5 due to incorrect IP address being resolved for the host name provided by the target EAP server
Issue
- Unable to monitor JBoss server instances from agent
-
Agent log contains the following error:
org.rhq.core.clientapi.agent.PluginContainerException: Failed to start component for resource Resource[id=31391, uuid=47a47bb2-329a-9413-c62f-080e80ecd8b8, type={JBossAS5}JBossAS Server, key=/opt/jboss/jboss-eap-5.1/jboss-as/server/production, name=EAP somehost.net:1099 production, parent=somehost.net, version=EAP 5.1.2]. ... Caused by: org.rhq.core.pc.inventory.TimeoutException: [Warning] Call to [org.rhq.plugins.jbossas5.ApplicationServerComponent.start()] with args [[org.rhq.core.pluginapi.inventory.ResourceContext@239e2011]] timed out after 60000 milliseconds - invocation thread will be interrupted. -
Agent is unable to connect to EAP instance due to:
Caused by: java.net.ConnectException: Connection timed out
Environment
- Red Hat JBoss Operations Network (ON) 3.1
- Red Hat JBoss Enterprise Application Platform (EAP) 5
- JBoss EAP management plug-in for JBoss ON
- JBoss EAP managed server started using a bind address of
0.0.0.0 - JBoss EAP managed server's host has a host name which is resolving to an IP address of a different host - For example:
- Domain Name System (DNS) may be incorrectly configured and is returning the wrong IP address
- The host has a host mapping entry in its
etc/hostsfile which provides the wrong IP address for the host's host name
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
