Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1127386

Summary: ERROR [ClientCommandSenderTask Timer Thread #12] (enterprise.communications.command.client.JBossRemotingRemoteCommunicator)
Product: [JBoss] JBoss Operations Network Reporter: Matt Mahoney <mmahoney>
Component: AgentAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED NOTABUG QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.3.0CC: hrupp, mmahoney
Target Milestone: DR02   
Target Release: JON 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-03 18:30:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
agent.log none

Description Matt Mahoney 2014-08-06 19:26:43 UTC
Created attachment 924579 [details]
agent.log

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

ERROR [ClientCommandSenderTask Timer Thread #12] (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):
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 1 Heiko W. Rupp 2014-08-26 11:24:13 UTC
*** Bug 1127387 has been marked as a duplicate of this bug. ***

Comment 2 Heiko W. Rupp 2014-08-26 11:25:36 UTC
Looks like there was no server available to connect to:

Can not connect http client invoker after 1 attempt(s) -> java.net.ConnectException:Connection refused

If we should not display that error, how should the user ever find out that there is a problem?

Comment 3 Heiko W. Rupp 2014-08-26 11:28:29 UTC
*** Bug 1127383 has been marked as a duplicate of this bug. ***

Comment 4 Red Hat Bugzilla 2023-09-14 02:45:13 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days