StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POQuartz: skipping duplicate job fires scheduled with same fire time
primarykey
Id
19733981
data
AcceptedAnswerId
19734348
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-01T19:26:26.853
FavoriteCount
0
LastActivityDate
2015-08-26T10:38:42.723
LastEditDate
2013-11-01T19:32:18.843
LastEditorUserId
809107
OwnerUserId
809107
ParentId
0
PostTypeId
1
Score
2
ViewCount
2195
LastEditorDisplayName
text
Body
I'm new to Quartz and stuck on duplicate job runs. They was caused by two triggers which has overlapping fire times. Is there any Quartz "out-of-the-box" functionality which will prevent duplicate fires of same job with multiple attached triggers? Or maybe there is some third-party <code>Trigger</code> implementation which allows to combine schedule's with proper fire time calculation which will prevent duplicate fire times? Or maybe i can somehow combine multiple schedules? Any solution will be greatly appreciated. Thanks For the clarity: <pre><code>public static class MyJob implements Job { @Override public void execute(JobExecutionContext context) throws JobExecutionException { System.out.println("My Job at " + DateUtils.toDateTimeString(context.getFireTime()) + " by " + context.getTrigger().getKey().getName()); } } startScheduler() { final Set<Trigger> triggers = new HashSet<Trigger>(); triggers.add(TriggerBuilder.<CronScheduleBuilder>newTrigger().withIdentity("every 3 secs"). withSchedule(CronScheduleBuilder.cronSchedule("0/3 * * * * ? *")).build()); triggers.add(TriggerBuilder.<CronScheduleBuilder>newTrigger().withIdentity("every 2 secs"). withSchedule(CronScheduleBuilder.cronSchedule("0/2 * * * * ? *")).build()); final Scheduler scheduler = new StdSchedulerFactory(properties).getScheduler(); scheduler.scheduleJob(JobBuilder.newJob(MyJob.class).build(), triggers, false); scheduler.start(); } </code></pre> And the logs: <ul> <li>My Job at 01.11.2013T23:19:26.000 by every 2 secs</li> <li>My Job at 01.11.2013T23:19:27.000 by every 3 secs</li> <li>My Job at 01.11.2013T23:19:28.000 by every 2 secs</li> <li>My Job at 01.11.2013T23:19:30.000 by every 2 secs</li> <li>My Job at 01.11.2013T23:19:30.001 by every 3 secs</li> <li>My Job at 01.11.2013T23:19:32.000 by every 2 secs</li> <li>My Job at 01.11.2013T23:19:33.000 by every 3 secs</li> <li>My Job at 01.11.2013T23:19:34.000 by every 2 secs</li> <li>My Job at 01.11.2013T23:19:36.000 by every 2 secs</li> <li>My Job at 01.11.2013T23:19:36.001 by every 3 secs</li> <li>My Job at 01.11.2013T23:19:38.000 by every 2 secs</li> <li>My Job at 01.11.2013T23:19:39.000 by every 3 secs</li> <li>My Job at 01.11.2013T23:19:40.000 by every 2 secs</li> <li>My Job at 01.11.2013T23:19:42.001 by every 2 secs</li> <li>My Job at 01.11.2013T23:19:42.002 by every 3 secs</li> </ul>
Tags
<java><quartz-scheduler>
Title
Quartz: skipping duplicate job fires scheduled with same fire time
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USacc15
UserOwnerUserId
1. USacc15
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.