Bug 1074465 - Agent availability is unknown and NoSuchMethodException is being thrown to the agent log
Summary: Agent availability is unknown and NoSuchMethodException is being thrown to th...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent, Core Server
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: RHQ 4.10
Assignee: Thomas Segismont
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-10 10:13 UTC by Filip Brychta
Modified: 2014-04-23 12:32 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-23 12:32:26 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 918207 0 medium CLOSED Uninventorying resources for agents, on unreachable networks or waiting for registration, causes database hang 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1074470 0 unspecified CLOSED Agent disappeared from list of registered agents and corresponding imported platform resource disappeared as well 2021-02-22 00:41:40 UTC

Internal Links: 918207 1074470

Description Filip Brychta 2014-03-10 10:13:34 UTC 
Description of problem:
There is a following HA set up:
   server1 with agent1
   server2 with agent2
   agent3 connected to server1
   agent4 connected to server2

Agent1 and agent3 status was displayed as unknown and following exception was being thrown to agent logs:
2014-03-10 05:31:44,232 WARN  [WorkerThread#0[10.16.23.111:57014]] (command.impl.remotepojo.server.RemotePojoInvocationCommandService)- {RemotePojoInvocationCommandService.remote-pojo-execute-failure}Failed to execute a remote pojo invocation. Cause: java.lang.NoSuchMethodException: There is no remote POJO that can service the method invocation request. Command: Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.security-token=toJreHSQlYuSIIWOqxB3N+gW4193a34qeiJKrwRFaCxGsAdaNs4rH3ey3/FKTgiV/Po=, rhq.timeout=5000, rhq.send-throttle=true}]; params=[{invocation=NameBasedInvocation[ping], targetInterfaceName=org.rhq.core.clientapi.agent.ping.PingAgentService}]  

Version-Release number of selected component (if applicable):
Version :	
4.10.0-SNAPSHOT
Build Number :	
b93920c

How reproducible:
2/2 by automation


Additional info:
Complete server1 log http://jenkins.jonqe.lab.eng.bos.redhat.com:9080/job/rhq-master-core/490/artifact/logs/auto-rhq.bc.jonqe.lab.eng.bos.redhat.com-server.log

agent1.log - http://jenkins.jonqe.lab.eng.bos.redhat.com:9080/job/rhq-master-core/490/artifact/logs/auto-rhq.bc.jonqe.lab.eng.bos.redhat.com-agent.log

agent3.log - http://jenkins.jonqe.lab.eng.bos.redhat.com:9080/job/rhq-master-core/490/artifact/logs/auto-rhq-eap5-2.bc.jonqe.lab.eng.bos.redhat.com-agent.log
Comment 1 John Mazzitelli 2014-03-10 13:30:41 UTC 
i think this is already fixed - thomas s. found it Friday and if he hasn't checked in the fix yet, he will.
Comment 2 Thomas Segismont 2014-03-10 14:08:43 UTC 
Fixed in master on Friday, your build is based on an earlier commit (b93920c)

commit d8e07cc0b678e513e97d6321a1f6095f0b3a576c
Author: Thomas Segismont <tsegismo>
Date:   Fri Mar 7 17:24:04 2014 +0100

Bug 918207 - Add missing agent service definition in org.rhq.core.pc.PluginContainer#services
Comment 3 Heiko W. Rupp 2014-04-23 12:32:26 UTC 
Bulk closing of 4.10 issues.

If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.
Note You need to log in before you can comment on or make changes to this bug.