Skip to main content

Quartz stop a job

Quartz did a good job on implementing this concept. It was very easy to add this feature by implementing a base class that abstract the details of interrupt and have every job extend this class. If you can rely on thread.interrupt() then its the best way to interrupt a job that is blocked on some I/O or native call. However if its a normal job then a simple boolean flag would do the work.

You would need to use scheduler.interrupt(jobName, groupName); to interrupt a running Quartz job.


public abstract class BaseInterruptableJob implements InterruptableJob {
 private static final AppLogger logger = AppLogger.getLogger(BaseInterruptableJob.class); 
 private Thread thread;
 @Override
 public void interrupt() throws UnableToInterruptJobException {
  logger.info("Interrupting job " + getClass().getName());
  if (thread != null) {
   thread.interrupt();
  }
 }

 @Override
 final public void execute(JobExecutionContext context) throws JobExecutionException {
  try {
   thread = Thread.currentThread();
   interruptableExecute(context);
  } finally {
   thread = null;
  }
 }
 
 protected abstract void interruptableExecute(JobExecutionContext context) throws JobExecutionException;

}

Comments

  1. package net.nighttale.scheduling;

    import org.quartz.*;

    public class QuartzReport implements Job {

    public void execute(JobExecutionContext cntxt)
    throws JobExecutionException {
    System.out.println(
    "Generating report - " +
    cntxt.getJobDetail().getJobDataMap().get("type")
    );
    //TODO Generate report
    }

    public static void main(String[] args) {
    try {
    SchedulerFactory schedFact
    new org.quartz.impl.StdSchedulerFactory();
    Scheduler sched schedFact.getScheduler();
    sched.start();
    JobDetail jobDetail
    new JobDetail(
    "Income Report",
    "Report Generation",
    QuartzReport.class
    );
    jobDetail.getJobDataMap().put(
    "type",
    "FULL"
    );
    CronTrigger trigger new CronTrigger(
    "Income Report",
    "Report Generation"
    );
    trigger.setCronExpression(
    "0 0 12 ? * SUN"
    );
    sched.scheduleJob(jobDetail, trigger);
    } catch (Exception e) {
    e.printStackTrace();
    }
    }
    }

    How stop Job here any suggestion please?

    ReplyDelete
  2. well from the program it seems you are running a main program and not a web application so the only way you can stop this is to start another thread in application that is listening a port for some commands and when you receive the stop command you can stop your scheduler. Or you can embed a mini http server in the app and then use the request parameter to trigger the stop.

    ReplyDelete

Post a Comment

Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are
Download ErlangDownload Rabbit MQ ServerDownload Rabbit MQ Java client jarsCompile and run the below two class and you are done.
This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time.

For more information on AMQP, Exchanges, Queues, read this excellent tutorial
http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/

+++++++++++++++++RabbitMQProducer.java+++++++++++++++++++++++++++
import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost("127.0.0.1"); factory.setPort(5672); Conne…

Logging to Graphite monitoring tool from java

We use Graphite as a tool for monitoring some stats and watch trends. A requirement is to monitor impact of new releases as build is deployed to app nodes to see if things like
1) Has the memcache usage increased.
2) Has the no of Java exceptions went up.
3) Is the app using more tomcat threads.
Here is a screenshot

We changed the installer to log a deploy event when a new build is deployed. I wrote a simple spring bean to log graphite events using java. Logging to graphite is easy, all you need to do is open a socket and send lines of events.
import org.slf4j.Logger;import org.slf4j.LoggerFactory; import java.io.OutputStreamWriter; import java.io.Writer; import java.net.Socket; import java.util.HashMap; import java.util.Map; public class GraphiteLogger { private static final Logger logger = LoggerFactory.getLogger(GraphiteLogger.class); private String graphiteHost; private int graphitePort; public String getGraphiteHost() { return graphiteHost; } public void setGraphite…

Jersey posting multipart data

This took me sometime to figure out mostly it was because I was only including jersey-multipart-1.6.jar but I was not including mimepull-1.3.jar.

So the intent is to upload a file using REST api and we need pass meta attributes in addition to uploading the file. Also the intent is to stream the file instead of first storing it on the local disk. Here is some sample code.
@Path("/upload-service") public class UploadService { @Context protected HttpServletResponse response; @Context protected HttpServletRequest request; @POST @Consumes(MediaType.MULTIPART_FORM_DATA) @Produces(MediaType.APPLICATION_JSON) public String uploadFile(@PathParam("fileName") final String fileName, @FormDataParam("workgroupId") String workgroupId, @FormDataParam("userId") final int userId, @FormDataParam("content") final InputStream content) throws JSONException { //.......Upload the file to S3 or netapp or any storage service } }
Now to tes…