Is it possible to remove the misfire threshold?

[Matt]

Is it possible to remove the misfire threshold? I don't want a job to
ever be passed over b/c its fire time is outside the threshold. It is
just adding a layer of complexity for me.

Thanks,

Matt

[Marko Lahma]

Hi.

You should get away by using proper misfire instruction for your
trigger(s) or by setting misfire threshold to TimeSpan.Zero.

Hope this helps,

-Marko

[Jo]

I have a primary job in a Windows service that runs off a cron trigger. It creates hundreds of secondary jobs and triggers, adds them to the scheduler, and then terminates. These secondary jobs each take a few seconds to complete and are set to FireNow on a misfire.

I want the secondary jobs to be executed in the order they were scheduled (first-in-first-out). And if the host server goes offline, I'd like these scheduled jobs to resume firing, one at a time, on restart of the service and scheduler.

I have Quartz configured to run on a single thread using AdoJobStore. I'm having problems with the misfireThreshold. If I set it to something small like 1000 (1sec) then Quartz adds multiple consecutive entries of "Handling xx trigger(s) that missed their scheduled fire-time" to the output log. It also does not fire all scheduled jobs and fires them out of sequence.

Of course if I set a large value for misfireThreshold to remove these log entries, then Quartz will skip over the first few scheduled jobs.

So how do I effectively remove the effect of the misfireThreshold value? I simiply want the scheduler to process available jobs one by one in the order they were scheduled, until they're all executed.

I think there's a way to sequence jobs in v2.0 but I'd like to get the FIFO approach working if possible. Thanks.

[Amit Khot]

You should probably drop the jobs in a FIFO queue instead of creating as many quartz jobs.

Have one quartz thread (or multiple threads) service that queue.

Not sure if I'm missing something else here.

Amit.

--
You received this message because you are subscribed to the Google Groups "Quartz.NET" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quartznet+...@googlegroups.com.
To post to this group, send email to quar...@googlegroups.com.
Visit this group at http://groups.google.com/group/quartznet?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Jo Yoshida]

Thanks Amit. I wanted each job associated with a task (sending a fax) and have Quartz reschedule any on restart should the Windows service shut down before all of them were sent out.

With a queue, the primary job would need to maintain which faxes were sent or not. I don't think it would be difficult to implement but it's not zero effort. :p