Red Hat Bugzilla – Bug 535353
measurement collector thread not dying
Last modified: 2013-09-02 03:17:52 EDT
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.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2058
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.
new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
Mazz, what would it take to fix this?
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.
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.
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.