Bug 1127387 - ERROR [ClientCommandSenderTask Timer Thread #4] (enterprise.communications.command.client.JBossRemotingRemoteCommunicator)-
Summary: ERROR [ClientCommandSenderTask Timer Thread #4] (enterprise.communications.co...
Keywords:
Status: CLOSED DUPLICATE of bug 1127386
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Agent
Version: JON 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: DR02
: JON 3.3.0
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-06 19:28 UTC by Matt Mahoney
Modified: 2014-08-26 11:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-26 11:24:13 UTC
Type: Bug
Embargoed:

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

Description Matt Mahoney 2014-08-06 19:28:33 UTC 
Created attachment 924580 [details]
agent.log

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

ERROR [ClientCommandSenderTask Timer Thread #4] (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 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):


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:
Errors in agent.log after clean install/start.

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

Additional info:
Comment 2 Heiko W. Rupp 2014-08-26 11:24:13 UTC 

*** This bug has been marked as a duplicate of bug 1127386 ***
Note You need to log in before you can comment on or make changes to this bug.