Skip to main content

Is possible to postpone trigger fire in Quartz?



I have two processes:





Process 1 - implements runnable and can run forever. Process 2 - fires at fixed hour and minute of day (i've created a job that run with Quartz).





To warn the process 1 that the other process is running I can use the TriggerListener , but how can I postpone the fire of the second process if the process 1 still doing something?





For example: I need to fire the trigger at 2PM, but this need to be done after 2PM if the process 1 isnt idle.





Here's some sample:





ProcessForever.java







import static org.quartz.CronScheduleBuilder.dailyAtHourAndMinute;

import static org.quartz.JobBuilder.newJob;

import static org.quartz.TriggerBuilder.newTrigger;



public class ProcessForever implements Runnable {



private boolean processTwoRunning;

private Scheduler scheduler;

private Trigger trgProcessTwo;

private String status;



public static final STATUS_PROCESS = "PROCESS";

public static final STATUS_SLEEP = "SLEEP";



private static Logger LOGGER = Logger.getLogger( ProcessForever.class.getName() );



public void init() throws SchedulerException {

SchedulerFactory fact = new StdSchedulerFactory();

scheduler = fact.getScheduler();

}



@Override

public void run() {

try {

scheduler.start();

buildTrigger();

while( true ) {

//do something and then sleep for some time.

//the Quartz trigger should fire only in STATUS_SLEEP...

setStatus( STATUS_PROCESS );

try { Thread.sleep(120 * 1000); }catch(Exception e){}

setStatus( STATUS_SLEEP );

}catch( Exception e ) {

e.printStackTrace();

}

}



private void buildTrigger() throws SchedulerException {

LOGGER.info("defineCargaDadosTrigger()");

JobDetail dt = newJob( ProcessTwo.class )

.withIdentity("coleta","grpcoleta")

.build();



trgProcessTwo = newTrigger().withIdentity(

new TriggerKey("triggerProcessTwo") )

.forJob( dt )

.startNow()

.withSchedule( dailyAtHourAndMinute(13,31) )

.build();

KeyMatcher<TriggerKey> m = KeyMatcher.keyEquals( trgProcessTwo.getKey() );

scheduler.scheduleJob(dt, trgProcessTwo );

//this will notice the process 1 that the trigger is running...

//scheduler.getListenerManager().addTriggerListener(someclass, m );

}



//getters & setters ommited...



}







ProcessTwo.java







import org.quartz.Job;

import org.quartz.JobExecutionContext;

import org.quartz.JobExecutionException;

/**

ProcessTwo cannot run concurrent with ProcessForever...

*/

public ProcessTwo implements Job {

@Override

public void execute(JobExecutionContext arg0) throws JobExecutionException {

System.out.println("Doing something...");

try { Thread.sleep(10000); } catch( InterruptedException i ){}

System.out.println("Stop doing something...");

}

}




Comments

  1. That's quite a common question in Quartz. Here are some hints provided by the FAQ

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex