Bug 1127388 - ERROR [InventoryManager.discovery-1] (enterprise.communications.command.client.ClientCommandSenderTask)
Summary: ERROR [InventoryManager.discovery-1] (enterprise.communications.command.clien...
Status: CLOSED DUPLICATE of bug 1127414
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Agent
Version: JON 3.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: DR02
: JON 3.3.0
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
Depends On:
TreeView+ depends on / blocked
Reported: 2014-08-06 19:31 UTC by Matt Mahoney
Modified: 2014-08-26 12:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-08-26 12:18:37 UTC
Type: Bug

Attachments (Terms of Use)
agent.log (465.70 KB, text/plain)
2014-08-06 19:31 UTC, Matt Mahoney
no flags Details

Description Matt Mahoney 2014-08-06 19:31:01 UTC
Created attachment 924581 [details]

Description of problem:
Error in agent.log file after clean install and server start.

ERROR [InventoryManager.discovery-1] (enterprise.communications.command.client.ClientCommandSenderTask)- {ClientCommandSenderTask.send-failed}Failed to send command [Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.agent-name=mm-jon33dr01-t3.bc.jonqe.lab.eng.bos.redhat.com, rhq.externalizable-strategy=AGENT, rhq.security-token=mIxENEDslSrspUG0qY3jsvl6Vt5WQv5zERSbvuNzyyF+b+sQyk+XKS0XZ45jlbtLb20=, rhq.timeout=0, rhq.send-throttle=true}]; params=[{invocation=NameBasedInvocation[getResourceSyncInfo], targetInterfaceName=org.rhq.core.clientapi.server.discovery.DiscoveryServerService}]]. Cause: org.jboss.remoting.CannotConnectException:Can not connect http client invoker after 1 attempt(s) -> java.net.ConnectException:Connection refused. Cause: org.jboss.remoting.CannotConnectException: Can not connect http client invoker after 1 attempt(s)

Version-Release number of selected component (if applicable):
JON 3.3 DR01

How reproducible:

Steps to Reproduce:
1. Install and start JON

Actual results:
Errors in agent.log after clean install/start.

Expected results:
Should be zero silent Errors in agent.log

Additional info:

Comment 1 Heiko W. Rupp 2014-08-26 12:18:37 UTC
If there is no server to connect to and we silence this error, how is the user supposed to learn about the erroneous condition?

*** This bug has been marked as a duplicate of bug 1127414 ***

Note You need to log in before you can comment on or make changes to this bug.