Quartz.Net Trigger Scheduled Job On Demand

quartz-schedulerquartz.net

I have some Quartz.Net jobs which are running on a Schedule

scheduler.ScheduleJob(
new JobDetailImpl("MarkAsSolutionReminderJob", typeof(MarkAsSolutionReminderJob)),
new CalendarIntervalTriggerImpl("MarkAsSolutionReminderJobTrigger", IntervalUnit.Hour, 6));

Is it possible for me to manually trigger this Job to run when I want it to?

So it continues to run as normal, but in a specific piece of code I might want to just run it out of schedule once or twice. But it doesn't affect the scheduled job?

Best Answer

Is it possible for me to manually trigger this Job to run when I want it to?

Yes, you can trigger this job as and when you need.

Use void TriggerJob(JobKey jobKey) method for this as below:

scheduler.TriggerJob(new Jobkey("MarkAsSolutionReminderJob"));

If you want to pass some data to the job while executing it on demand, you can also do that by just using another overload void TriggerJob(JobKey jobKey, JobDataMap data); of the same method as below:

Dictionary<string, string> data = new Dictionary<string, string>();
//populate dictionary as per your needs
JobDataMap jobData = new JobDataMap(data);
scheduler.TriggerJob(new Jobkey("MarkAsSolutionReminderJob"),jobData);

Related Solutions

R – Quartz.Net Thread Pools

Another suggestion, when the job fires, spin another thread off to do the work, so you can return the job thread to the Quartz pool.

Use a bounded thread pool for the worker threads, so you don't get too many worker threads running at the same time.

See, java.util.concurrent for the Executor and ThreadPool classes. It's a more complicated solution, but may scale better.

.net – In Quartz.NET is there a way to set a property that will only allow one instance of a Job to run

Use the DisallowConcurrentExecution attribute.

Declare your class as follows:

[DisallowConcurrentExecution]
public class SomeTask : IJob
{

}

Misfires

"Misfire Instructions Another important property of a Trigger is its "misfire instruction". A misfire occurs if a persistent trigger "misses" its firing time because of the scheduler being shutdown, or because there are no available threads in Quartz.NET's thread pool for executing the job. The different trigger types have different misfire instructions available to them. By default they use a 'smart policy' instruction - which has dynamic behavior based on trigger type and configuration. When the scheduler starts, it searches for any persistent triggers that have misfired, and it then updates each of them based on their individually configured misfire instructions. When you start using Quartz.NET in your own projects, you should make yourself familiar with the misfire instructions that are defined on the given trigger types, and explained in their API documentation. More specific information about misfire instructions will be given within the tutorial lessons specific to each trigger type."

Check out the "trigger misfire instructions" information at the bottom of these pages:

Lesson 5: SimpleTrigger

Lesson 6: CronTrigger

Old Quartz.NET API answer:

http://quartznet.sourceforge.net/apidoc/topic142.html:

IStatefulJob instances follow slightly different rules from regular IJob instances. The key difference is that their associated JobDataMap is re-persisted after every execution of the job, thus preserving state for the next execution. The other difference is that stateful jobs are not allowed to Execute concurrently, which means new triggers that occur before the completion of the IJob.Execute method will be delayed.

So, declare your 'Job' class as follows:

class DocumentImportJob : IStatefulJob
{
   ......
}

To avoid delayed tasks re-firing immediately after job completes (when the job takes more than 1 minute and causes a trigger 'misfire'), do the following when creating your trigger(s) (adjust depending on the trigger type used):

myJobTrigger.MisfireInstruction = MisfireInstruction.CronTrigger.DoNothing;

https://www.quartz-scheduler.net/documentation/quartz-2.x/tutorial/more-about-triggers.html

Best Answer

Related Solutions

R – Quartz.Net Thread Pools

.net – In Quartz.NET is there a way to set a property that will only allow one instance of a Job to run

Related Topic