quartz-scheduler

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); sched.start(); } } Here i am implementing InterruptableJob like public class MyJob implements

What I'm trying to achieve: I have a secondly trigger that fires every 5 secods, and stateful job, that takes sometimes more than 5 seconds (7 for example) and what I have now start: 00:00:00 end : 00:00:07 start: 00:00:07 < right after previous has finished what I want : start: 00:00:00 it should run at 00:00:05 but it hasn't end : 00:00:07 start: 00:00:10 (5 seconds after previous, successive or not) I have tried quartz.net version 2 and 1. Job: [PersistJobDataAfterExecution] [DisallowConcurrentExecution] public class StatefulJob : IJob (or IStatefulJob in 1.x version) { public void Execute

I have a shell script which I'd like to trigger from a J2EE web app. The script does lots of things - processing, FTPing, etc - it's a legacy thing. It takes a long time to run. I'm wondering what is the best approach to this. I want a user to be able to click on a link, trigger the script, and display a message to the user saying that the script has started. I'd like the HTTP request/response cycle to be instantaneous, irrespective of the fact that my script takes a long time to run. I can think of three options: Spawn a new thread during the processing of the user's click. However, I don't

I have an OSGI scheduler bundle that has the Quartz Scheduler Jar in it. This bundle exposes just an application interface to other bundles and, when a new job is registered, it is wrapped into a temporaryJob (that implements StatefulJob) and scheduled using the scheduler. In this way I don't have to expose Quartz Scheduler jar (that it is not so much osgi compliant). The problem with this approach is that, since StatefulJob avoids to execute job in parallel and I have only one actual job (the temporaryJob), all my real jobs run one at a time. Unfortunately it seems that the marker interface

When my process gets a message, it needs to start a timer and execute some logic in X seconds. These jobs need to be stored in a JDBC store, which as far as I can tell may be irrelevant to this question. Based on what I've read, I should be able to assign a JobDataMap with different values for similar properties to a single Job class, but I'm unable to find any documentation or examples to back this use-case. Perhaps my Google-fu is weak. Does that make sense? Have one Job class and somehow store a JobDataMap to populate that Job class and run it on a per-message basis? Uriah Carpenter org

I'm trying to set up Quartz for the first time, and forgive me if I am just not understanding something. I'm wondering what is the best way to accomplish the following: How to set up a job that must run a daily email report, and also be able to recover from a missed trigger so that: 1) the job knows what day the trigger was SUPPOSED to fire on. and 2) if (god forbid) the server is down for 3 days, Quartz will recover by running three missed days consecutively, also informing the job of what day each job represents. (execution order is not really important as long as I know what day each

i'm stuck trying to turn off the annoying DEBUG logging of quartz. i'm using log4j as logging framework and i've already tried to add this line to the lg4j proprieties file "log4j.logger.org.quartz=ERROR" i'm still getting tons of these debugging logging messages 13:35:44.680 [MyScheduler_QuartzSchedulerThread] DEBUG o.quartz.core.QuartzSchedulerThread - batch acquisition of 0 triggers how can i turn this function off ? EDIT. i've moved my configuration to xml file...but still getting the same annoying problem <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE log4j:configuration SYSTEM "log4j

I have an issue with shutting down a Grails app in production. It shuts down cleanly when running from IntelliJ. But on a standalone Tomcat 7, shutting down gets it into a zombie state where the java process still exists but HTTP requests hang. I have to kill the java process (using kill). I'm using Tomcat's standard bin/startup.sh and shutdown.sh. With Tomcat stopped, I drop the .war into Tomcat's /webapps directory and then start. I suspect it could be the Quartz job scheduler plugin, but I deployed a version with no jobs in grails-app/jobs and it still hangs. Anybody run across this before?