Bugzilla – Bug 4655
EntrySweeper should be a daemon thread
Last modified: 2006-08-18 15:33:50
You need to
before you can comment on or make changes to this bug.
globus-stop-container does not stop the container's jvm if
AggregatorServiceGroupResource.EntrySweeper is running as a non-daemon thread.
Fix is trivial:
this.sweeperInterval = getConfiguration().getEntrySweeperInterval();
//Set Daemon flag before starting the thread
A related question:
Should EntrySweeper be a TimerListener task to be used with the TimerManager
supplied with the container? Seems like it would be an easy change.
Will convert EntrySweeper to TimerListener in HEAD and will update 4.0.x
branches to use setDaemon(true). Thanks Shishir.
Fixed the 4.0.x branch to use setDaemon(true). It looks like the code in 4.1.x
and HEAD has the proper thread termination code in it and functions correctly
when using globus-stop-container. I will likely still change the code in HEAD
to use TimerLister interface instead of Thread for consistency, but it is not a
bug at the moment.