Bug 535353 (RHQ-2058)

Summary:	measurement collector thread not dying
Product:	[Other] RHQ Project	Reporter:	John Mazzitelli <mazz>
Component:	Plugin Container	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	cwelton, sdharane
Target Milestone:	---	Keywords:	SubBug
Target Release:	---
Hardware:	All
OS:	All
URL:	http://jira.rhq-project.org/browse/RHQ-2058
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-02 07:17:52 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	565628

Description John Mazzitelli 2009-05-05 03:57:00 UTC

start an agent, get it collecting measurements and reporting things.

shutdown agent using "shutdown" command.

notice this thread is still around:

Daemon Thread [MeasurementManager.collector-1] (Suspended)	
	java.lang.Thread.sleep(long) line: not available [native method]	
	org.rhq.core.pc.measurement.MeasurementManager$MeasurementCollectionRequester.run() line: 171	
	java.util.concurrent.Executors$RunnableAdapter<T>.call() line: 441	
	java.util.concurrent.FutureTask$Sync.innerRun() line: 303	
	java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask<V>(java.util.concurrent.FutureTask<V>).run() line: 138	
	java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask<V>.access$301(java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask) line: 98	
	java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask<V>.run() line: 207	
	java.util.concurrent.ThreadPoolExecutor$Worker.runTask(java.lang.Runnable) line: 885	
	java.util.concurrent.ThreadPoolExecutor$Worker.run() line: 907	
	java.lang.Thread.run() line: 619	

this should die.

Comment 1 Red Hat Bugzilla 2009-11-10 20:56:53 UTC

This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2058

Comment 2 wes hayutin 2010-02-16 16:53:38 UTC

Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug

Comment 3 wes hayutin 2010-02-16 16:58:53 UTC

making sure we're not missing any bugs in rhq_triage

Comment 4 Corey Welton 2010-08-25 15:51:00 UTC

Mazz, what would it take to fix this?

Comment 5 John Mazzitelli 2010-08-25 16:25:10 UTC

this is already fixed by some unknown changes. Recently (within the past couple months) I did alot of testing where I shutdown and restarted the internals of the agent and I specifically looked at what threads were still hanging around and all threads were cleaned up that were expected to be cleaned up. No stray threads remained. So, I can say that at least in the latest code, this is no longer a problem.

this bz can be closed as fixed.

Comment 6 Sudhir D 2010-10-19 06:42:04 UTC

I tested the condition on the latest rhq-server-4.0.0-SNAPSHOT build. The issue seem to have resolved as mentioned by Mazz in the previous comment. 

Marking this as verified.

Comment 7 Heiko W. Rupp 2013-09-02 07:17:52 UTC

Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.