java quartz scheduler fire a new job immediately

Question

Is it possible to crate a job that will trigger immediately ? when i want the job to be triggres now i builed a cron expression string with the current date and time - i think it's too complicated, is there another way to trigger the job immediately ?

Thank's In Advance.

score 58 · Answer 1 · answered Mar 28 '12 at 11:20

58

Yeah, use the following Trigger to immediately fire your job instead of waiting upon the Cron Expressions.

    String jobName = ""; // Your Job Name
    String groupName = ""; // Your Job Group
    Trigger trigger = TriggerBuilder.newTrigger()
                .withIdentity(jobName, groupName)
                .startNow()
                .build();

answered Mar 28 '12 at 11:20

Rohit Bansal

1,199
1
10
18

6

Much better than creating a memory leak setting durable = true ;) – Bruno Medeiros Jul 09 '13 at 02:00

Ken Chan · Accepted Answer · 2012-03-27T15:08:37.073

36

All the Jobs registered in the Quartz Scheduler are uniquely identified by the JobKey which is composed of a name and group . You can fire the job which has a given JobKey immediately by calling triggerJob(JobKey jobKey) of your Scheduler instance.

//Create a new Job 
JobKey jobKey = JobKey.jobKey("myNewJob", "myJobGroup");
JobDetail job = JobBuilder.newJob(MyJob.class).withIdentity(jobKey).storeDurably().build();

//Register this job to the scheduler
scheduler.addJob(job, true);

//Immediately fire the Job MyJob.class
scheduler.triggerJob(jobKey);

Note :

scheduler is the Scheduler instance used throughout your application . Its start() method should be already called after it is created.
The job is the durable job which cannot attach any triggers or cron to it .It can only be fired programmatically by calling triggerJob(JobKey jobKey).

edited Mar 27 '12 at 15:08

answered Mar 27 '12 at 14:53

Ken Chan

84,777
26
143
172

Why not using `SimpleTrigger` and use `scheduler.scheduleJob()` which will result in immediate execution? – basZero Dec 31 '12 at 12:58
2

FYI JobKey is not part of the 1.5.2 API. – David Mann Jan 02 '14 at 20:23
1

The job has to be set durable (.storeDurably()) but then we have to clean it up manually (probably using scheduler.deleteJob()) or the job will stay persistently in the DB. I wonder how people deal with this problem? – leeyuiwah Mar 03 '14 at 22:49
Usually you don't want to firing the job concurrently. It is possible as you have scheduled the job, and then fire it immediately. If you are using the 2.x version, you can annotate your job class with @DisallowConcurrentExecution, but if you are using older versions, you can implement your job using the old StatefulJob interface. – Yuci May 06 '16 at 10:36

granadaCoder · Answer 3 · 2018-02-02T16:05:01.550

0

You can create the "JobKey" on the fly with the 2 key string values.

IScheduler sched = /* however you get your scheduler*/;

sched.TriggerJob(new JobKey("myname", "mygroup"));

edited Feb 02 '18 at 16:05

answered Feb 02 '18 at 02:35

granadaCoder

26,328
10
113
146

Please add at least a short description. – Valdi_Bo Feb 02 '18 at 07:36

java quartz scheduler fire a new job immediately

3 Answers3

Linked