quartz-scheduler

问题 I'm very new to Quartz, but know 3 simple things which you have to have in order to make it work. These are jobs, triggers and scheduler. Now, in our domino application we have to use it for refreshing a token. I've created 3 basic classes for it. The job: public class RefreshEGRZTokenJob implements Job { public void execute(JobExecutionContext arg0) throws JobExecutionException { System.out.println("stub for refreshing a token"); } } The trigger and something like main : public class

问题 I am new to Quartz . I did manage to figure out that default value for Scheduler configuration is org.quartz.threadPool.threadCount=-1 . But it did not find anywhere what this implies. Does this mean that there will be only one thread or has it some other 'number'? I am playing with quartz-scheduler v2.2. 回答1: It depends.. If you use Spring Framework then you can see that the real default is defined in SchedulerFactoryBean: public static final int DEFAULT_THREAD_COUNT = 10; In case of using

问题 I'm a java EE developer which has used until now frameworks like Quartz to schedule tasks. I can see that Java EE 7 features a ManagedScheduledExecutorService to schedule single or repeating tasks. As I have never used in real projects this new features I wonder if there are still advantages of using Quartz (or others) when you have a portable way to do it ? Thanks! 回答1: I believe that in future projects, there's really no need to use third-party libraries. Java EE 7 is full of scheduling

问题 I have unit test, i use guice for di, i annotate my class with : @Guice(modules = { BatchGuiceModule4Test.class }) public class TestOneDayBatchStarter { } My objects are well injected from my module like this one : @Inject private DataManager dataManager; In my module, I add a @Provides method : @Provides @Singleton public DataManager getDataManager() { LOG.debug("## init Mocked Data Manager"); DataManager dataManager = mock(DataManager.class); when(dataManager.getObjectCodeList()).thenReturn

问题 I am running a simple quartz job in main class which runs every 30 secs. public class Start { public static void main(String[] args) throws Exception { SchedulerFactory sf = new StdSchedulerFactory(); Scheduler sched = sf.getScheduler(); JobDetail job = newJob(MyJob.class).withIdentity("myJob","XXX").build(); Trigger trigger = TriggerBuilder.newTrigger() .withSchedule( SimpleScheduleBuilder.simpleSchedule() .withIntervalInSeconds(30) .repeatForever()) .build(); sched.scheduleJob(job, trigger)

问题 How do I automatically trigger Java function to stop Quartz scheduler jobs when I deploy/undeploy/redeploy JEE5 application in Glassfish. 回答1: Implement ServletContextListener and hook on contextDestroyed() . Basic example: public class Config implements ServletContextListener { public void contextInitialized(ServletContextEvent event) { // Write code here which should be executed on webapp startup. } public void contextDestroyed(ServletContextEvent event) { // Write code here which should be

问题 I want to use Quartz Scheduler framework in my application. I came across two types of JobStores: 1) RAM Job Store 2) JDBC Job store. I am wondering in which case I have to use which job store. And what is the pros and cons between them. Any thoughts on this is really helpful for me and I appreciate it. 回答1: JDBC job store saves information about fired triggers and jobs in the database, thus: it won't lose firings if application was down when trigger was suppose to fire (this depends on

问题 HashedWheelTimers are based on this 1987 paper about how traditional timers consume O(N) processing to maintain (for N timers), but hashed wheels can consume O(1). I'm unsure if Quartz's job scheduling just managers timers underneath, or actually uses an O(1) solution under the covers. 回答1: The Quartz scheduler is designed for scheduling persistent jobs. So, when Quartz comes up after going down, it can see what jobs were supposed to run but didn't and optionally run th em. HashedWheelTimer

问题 I have run into a case where I have to use a persistent Scheduler , since I have a web application that can crash or close due to some problems and might lose it job details if this happens . I have tried the following: Use Quartz scheduler : I used RAMJobStore first, but since it isn't persistent, it wasn't of much help. Can't setup JDBCJobStore because, this will require huge code changes to my existing code base. In light of such a scenario, I have the following queries: If I use Spring's

问题 I am using Spring quartz Scheduler but I am not using an XML file. I want to create the entire configuration programmatically. I have written the following code. package com.eaportal.service.impl; import java.text.ParseException; import java.util.Date; import java.util.HashMap; import java.util.Map; import org.quartz.JobDetail; import org.springframework.scheduling.SchedulingException; import org.springframework.scheduling.quartz.CronTriggerBean; import org.springframework.scheduling.quartz