Agent is unable to connect to JBoss ON server because initialization callback is failing due to a network connection failure
Issue
- Agent not starting cleanly
- The agent fails to connect to the server and the following message is logged:
ERROR [RHQ Server Polling Thread] (enterprise.communications.command.client.JBossRemotingRemoteCommunicator)- {JBossRemotingRemoteCommunicator.init-callback-failed}The initialize callback has failed. It will be tried again. Cause: org.jboss.remoting.CannotConnectException:Can not connect http client invoker. Connection timed out. -> java.net.ConnectException:Connection timed out
org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Connection timed out.
- Agent log contains the following warning:
WARN [RHQ Server Polling Thread] (org.rhq.enterprise.agent.FailoverFailureCallback)- {AgentMain.too-many-failover-attempts}Too many failover attempts have been made [1]. Exception that triggered the failover: [org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Connection timed out.]
- Agent can not connect to server if it is unable to resolve the server's end-point address
- I have installed JON and RHQ-Agents. All Agents were available in JON console when I had last logged in to JON. Now, all Agent appear unavailable though they are up and running
Environment
- Red Hat JBoss Operations Network (JON)
- 3.1
- 3.2
- 3.3
- JBoss ON agent attempting to register or connect to a JBoss ON server
- JBoss ON server's host name or IP address is not resolvable or reachable from the agent host
- Agent's
rhq.agent.server.bind-addressproperty value - Server's end-point address as defined in the server topology administration page
- Agent's
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.
