Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

Fantastic, thanks! I look forward to the 1.7.1 release.

Hi James,

Should I file a bug report for this?

thanks,
Nagender

I would love to see this feature restored in Quartz. Is there a bug report I should file? Any ETA for when this feature may be restored?

thanks

Yes, this was using JDBC JobStore on MySQL.

Was the ordering of misfired triggers ever guaranteed? Based on what I found in the tutorial and Javadoc, I didn't see a misfire instruction for CronTrigger that would provide this feature.

thanks,
Nagender

Hi,
I’m using Quartz 1.6 with CronTriggers. I’d like to know the following -

Say a trigger t1 is scheduled for 10pm, and trigger t2 is scheduled for 10:05pm. If there are no available workers at 10pm, then t1 is misfired. If workers next get freed up only at 10:10pm, is there a way to ensure t1 is fired before t2?

In short, is there a way to retain the ordering of misfired triggers? Per http://www.quartz-scheduler.org/docs/tutorial/TutorialLesson06.html, it looks like the only two options are either:

1. MISFIRE_INSTRUCTION_FIRE_ONCE_NOW, which appears to be the default. It doesn’t seem to guarantee retaining the ordering

or

2. MISFIRE_INSTRUCTION_DO_NOTHING, I haven’t tried this yet

Is there a way to guarantee ordering of misfired triggers?

thanks,
Nagender

ps: I posted this question to users@quartz.dev.java.net yesterday but don't see my message on the archive page yet (https://quartz.dev.java.net/servlets/BrowseList?listName=users&by=date&from=2010-01-01&to=2010-01-31&first=1&count=3), is that the correct users email list?