Quartz Triggers re-firing before the last Job has completed execution...
Joined: Mar 29, 2006
I've configured a Quartz scheduler using Spring ContextLoaderListener. Everything is working fine, but I'm having a problem with Trigger "overlap".
When Trigger X fires, it kicks off Job X. IF Trigger X fires again, before Job X is complete, Job X will launch again, creating all sorts of race conditions, concurrency issues, Hibernate Sessions closing, dogs and cats living together in sin, etc.
How can I tell Trigger X to not launch the job, if the Job is already running?
I thought this was related to Trigger misfires, but apparantly that's something else entirely unrelated...
Joined: Nov 24, 2000
My guess is that you want to implement a TriggerListener, and provide an appropriate vetoJobExecution method to enforce the behaviour you want. See: