We have a simple situation with Quartz 1.6.0, where we are scheduling jobs, using the ram store. We schedule a job via a SimpleTrigger (to fire at some time in the near future). We pause the job; adding a new trigger to the schedule for the job (scheduleJob(Trigger)) results in the new trigger firing, even though the job is paused.
Looking at the underlying ram store, when a new trigger is added, it doesn't know if a job is in a paused state; when the pause of the job occurred, all existing triggers for that job were paused, but ... new triggers are free to fire.
Is this intended, or a bug?
I found a similar bug, recently fixed in 1.6.1, I think, where pausing a job group had the same issue, and a merge with some code from Quartz.NET was the fix. I think this fix should go further, and remember paused jobs (not just paused triggers).
If this is intended behavior, is there any workaround to get a newly added trigger immediately into a paused state?
Thanks!
j
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=394904&messageID=481964#481964---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@...
For additional commands, e-mail:
users-help@...
