Stateful Job Queue

144 views
Skip to first unread message

carlos

unread,
Mar 20, 2012, 7:54:14 PM3/20/12
to Quartz.NET
Marking a job as stateful should disallow the same jobs from running
on top of each other (I want this). Is it possible to limit the job
queue to say 1 job and any others are just dropped?

Nuno Maia

unread,
Mar 21, 2012, 10:04:34 AM3/21/12
to quar...@googlegroups.com
Hi,

You can limit the number of concurrent jobs by defining a proper value
in property "threadCount" and a missfire policy to skip the trigger
execution.

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

carlos

unread,
Mar 21, 2012, 12:59:31 PM3/21/12
to quar...@googlegroups.com
I don't want to limit the overall jobs running. I want to make it so if a new job is requested to run and there is already one of itself running and another queued to run after that one is done then it would just be dropped.


On Wednesday, March 21, 2012 7:04:34 AM UTC-7, Nuno Maia wrote:
Hi,

You can limit the number of concurrent jobs by defining a proper value
in property "threadCount" and a missfire policy to skip the trigger
execution.


On Tue, Mar 20, 2012 at 11:54 PM, carlos <cbd...@gmail.com> wrote:
> Marking a job as stateful should disallow the same jobs from running
> on top of each other (I want this).  Is it possible to limit the job
> queue to say 1 job and any others are just dropped?
>
> --
> You received this message because you are subscribed to the Google Groups "Quartz.NET" group.
> To post to this group, send email to quar...@googlegroups.com.

> To unsubscribe from this group, send email to quartznet+unsubscribe@googlegroups.com.

Nuno Maia

unread,
Mar 21, 2012, 4:32:36 PM3/21/12
to quar...@googlegroups.com
Ok, for that you can use the attrubute DisallowConcurrentExecution and a missfire to skip to next execution


On Wednesday, March 21, 2012, carlos <cbd...@gmail.com> wrote:
> I don't want to limit the overall jobs running. I want to make it so if a new job is requested to run and there is already one of itself running and another queued to run after that one is done then it would just be dropped.
>
> On Wednesday, March 21, 2012 7:04:34 AM UTC-7, Nuno Maia wrote:
>>
>> Hi,
>>
>> You can limit the number of concurrent jobs by defining a proper value
>> in property "threadCount" and a missfire policy to skip the trigger
>> execution.
>>
>> On Tue, Mar 20, 2012 at 11:54 PM, carlos <cbd...@gmail.com> wrote:
>> > Marking a job as stateful should disallow the same jobs from running
>> > on top of each other (I want this).  Is it possible to limit the job
>> > queue to say 1 job and any others are just dropped?
>> >
>> > --
>> > You received this message because you are subscribed to the Google Groups "Quartz.NET" group.
>> > To post to this group, send email to quar...@googlegroups.com.
>> > To unsubscribe from this group, send email to quartznet+...@googlegroups.com.

>> > For more options, visit this group at http://groups.google.com/group/quartznet?hl=en.
>> >
>
> --
> You received this message because you are subscribed to the Google Groups "Quartz.NET" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/quartznet/-/QRBViLq4zs8J.

> To post to this group, send email to quar...@googlegroups.com.
> To unsubscribe from this group, send email to quartznet+...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages