
|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
None
|
| Affects Version/s: |
1.5.2
|
| Fix Version/s: |
1.6
|
|
|
Environment:
|
Linux, java 1.5
|
|
Issue Links:
|
Related
|
|
This issue relates to:
|
|
QUARTZ-204
Need to daemonize scheduler thread, c...
|
|
|
|
|
|
|
|
We are having ear re-deploment problems under Jboss and found that the thread groups created by quarts were not getting cleanup. (Don't ask me why, the groups hang in there even after a re-deployment). If the thread groups are made daemons they will get auto destroyed when the last thread exists. Here is the modified function from QuartzScheduler.java (this thing works and the groups are cleaned up)
public ThreadGroup getSchedulerThreadGroup() {
if (threadGroup == null) {
threadGroup = new ThreadGroup("QuartzScheduler:"
+ getSchedulerName());
threadGroup.setDaemon(true);
}
return threadGroup;
}
|
|
Description
|
We are having ear re-deploment problems under Jboss and found that the thread groups created by quarts were not getting cleanup. (Don't ask me why, the groups hang in there even after a re-deployment). If the thread groups are made daemons they will get auto destroyed when the last thread exists. Here is the modified function from QuartzScheduler.java (this thing works and the groups are cleaned up)
public ThreadGroup getSchedulerThreadGroup() {
if (threadGroup == null) {
threadGroup = new ThreadGroup("QuartzScheduler:"
+ getSchedulerName());
threadGroup.setDaemon(true);
}
return threadGroup;
}
|
Show » |
|
We've actually already done similar work, and more (see linked issue).
Thanks for contributing though, we do appreciate users who do so!