Quartz CronTrigger ignores misfire policy and redirects every misfire

I created CronTrigger as follows

CronScheduleBuilder schedule = CronScheduleBuilder.cronSchedule(new CronExpression(CRON_EXPRESSION)).withMisfireHandlingInstructionDoNothing();

From what I read here about Cron Triggers , if I had a server shutdown during which it would normally be CronTrigger to start several times when the server returns to the network, I should run Quartz Job only with the next normally scheduled trigger fire.

This does not actually work as expected, and it does not matter which policy I set, I have a Job executed all the time when the trigger was skipped. Therefore, if the trigger is skipped 100 times, I get the task 100 times. Is this really a mistake or am I something wrong?

I am using Quartz-scheduler 2.2.1 in WebSphere with SimpleThreadPool, JobStoreTX, StdJDBCDelegate, isClustered = true, threadCount = 1

+4
source share

All Articles