Created attachment 924587 [details] agent.log Description of problem: Warning in agent.log file after clean install and server start. WARN [ClientCommandSenderTask Timer Thread #12] (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 after 1 attempt(s)] WARN [ClientCommandSenderTask Timer Thread #4] (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 after 1 attempt(s)] WARN [ClientCommandSenderTask Timer Thread #12] (org.rhq.enterprise.agent.AgentMain)- {AgentMain.failover-failed}Failed to failover to another server. Cause: org.jboss.remoting.CannotConnectException: Can not connect http client invoker after 1 attempt(s) WARN [ClientCommandSenderTask Timer Thread #4] (org.rhq.enterprise.agent.AgentMain)- {AgentMain.failover-failed}Failed to failover to another server. Cause: org.jboss.remoting.CannotConnectException: Can not connect http client invoker after 1 attempt(s) WARN [ClientCommandSenderTask Thread #6] (enterprise.communications.command.client.ClientCommandSenderTask)- {ClientCommandSenderTask.queuing-failed-command}The command that failed has its guaranteed-delivery flag set so it is being queued again Version-Release number of selected component (if applicable): JON 3.3 DR01 How reproducible: Steps to Reproduce: 1. Install and start JON. 2. 3. Actual results: Warnings in agent.log after clean install/start. Expected results: Should be zero silent Warnings in server.log Additional info:
Wow, l *** This bug has been marked as a duplicate of bug 1127414 ***