Quartz Scheduler - Jobs running past their next fire time.

[Aaron Mirsky]

This question was also posted on Terracotta's forum: http://forums.terracotta.org/forums/posts/list/0/4695.page#24039

I have a job that fires at a set interval and handled data. The amount of data is dynamic (can be a lot or a little) which means the job might take a lot or a little time to run.

What happens if lets say a job is scheduled to run every minute but task more than a minute to complete? Does a second instance of the job start running on another thread?

Basically, Is there a way to ensure that a specific Job A will only run if there is no other Job A already running?

Thanks in advance.

[Aaron Mirsky]

Got the answer on Terracotta,

I need to use StatefulJob instead of Job. This prevents the job from running concurrently.

link
http://forums.terracotta.org/forums/posts/list/4069.page
api
http://www.quartz-scheduler.org/docs/api/1.8.1/index.html