Trigger Misfire Reasons in Spring Job Scheduling

amy

Hi All,

We have developed a Spring stand alone application using Quartz based Spring Job scheduling functionality. Using RAMJobstore for storing the job details. We have deployed around 110 jobs of various functionality with different cron schedule. We have configured 12 quartz threads for serving 110 jobs.

Some times we are facing an issue of TRIGGER MISFIRE even there are scheduler threads available. We have implemented the TriggerListener to catch the MISFIREs. I can see at random times the Trigger MISFIRED even though quartz threads are available. I can see number of threads that are currently working that time by using the method 'shd.getCurrentlyExecutingJobs()'. The return value is not 12.

Please anyone let me know what are all the reasons for Trigger MISFIRE to happen? I suppose only reaason that is scheduler threads unavilability to serve the jobs. But, even there are sufficient threads available Trigger MISFIRE is happening.

Regards,
Sudhakar

I'm not an expert in quartz, but 110 jobs is a lot to have in one VM.  My guess would be the trigger is misfiring because the VM has no available resources, even if there are available threads in the pool, preventing the thread from even starting.  Have you thought about using a database job store instead?  That would allow you to have multiple VMs running to kick jobs off from.