Terracotta Discussion Forums

Hi,

I'm quite new to Quartz and may be asking something stupid right now. But I cannot find any information about preventing concurrent execution of different jobs.

I do have several jobs including group1.job1 (Job1.class) and group1.job2 (Job2.class) that must not run concurrent.

Can I tell Quartz somehow to wait with triggering one of these Jobs until the end of the other one if for some reason the other one is still running?

Thanks a lot,
Clemens

If you make your job "Stateful", then one of the sideeffect is NOT to be able run concurrently. See "StatefulJob" under http://quartz-scheduler.org/docs/1.x/tutorial/TutorialLesson03.html

Thank you for your reply.

I already read about stateful jobs. As far as I understand them, quartz prevents one stateful job to be executed in more than one instance concurrently.

I face the situation, that I have two (in fact six) different jobs that must not run concurrent. If Job1 (Job1.class implements Job) runs, Job2 (Job2.class implements Job) must wait until Job1 has finished.
IMHO quartz runs Job1 and Job2 parallel even if they are stateful. Or did I misunderstood stateful jobs?

Clemens

Have you considered to put your jobs in the same class and use job instance fonctionnality ?
You could use annotations like "DisallowConcurrentExecution" to prevent 2 job instances to run concurrently (see http://quartz-scheduler.org/docs/tutorial/TutorialLesson03.html)

It's just an idea, I've never done something like that and I don't know if it fits your need

This may help you too : http://www.quartz-scheduler.org/docs/faq.html#FAQ-chain

For what you describe Job1.class and Job2.class are not the same Job so you will not get the stateful behavior you are looking for.

If you were to schedule Job1.class to fire at 12:00 and then at 12:01 but first run still going then second run 12:01 will wait till previous one finishes. That is because you are scheduling the same Job with two different triggers. Which is not your case where you have 2 completely different jobs.

From the documentation (link posted by Jeh) I think your best option is

Another way is to build a Job that contains within its JobDataMap the name of the next job to fire, and as the job completes (the last step in its execute() method) have the job schedule the next job.

nicolas.loriente

Thanks for all suggestions.

After lots of reading and trying I will try the following strategy... Just in case someone else with similar questions reads this. ;-)

I implement one stateful job class as "master" and n jobs for the actual work.

I do only trigger master. Based on the trigger's name causing master to execute, master instantiates one of the n jobs and delegates the work.

This procedure allows me weaker coupling of the n jobs in terms of chaining and quartz grants the non-parallel execution.

The only open question is how to store the job configuration in the JobDataMap. I'm looking forward to store a configuration-map for each trigger in master's JobDataMap. If done, master can fetch the correct configuration and pass it to the delegate.

Greets, Clemens

This is an old thread and no update from a long time.Please let us know if you are still facing same issue.
Thanks