Skip to main content

Quartz Admin JSP

We use quartz for scheduling jobs on tomcat nodes, the job runs on a frequency rather then a set time so its helpful to know when is the next time the job will be fired and for testing purposes its good if we can fire the job manually instead of waiting for the trigger to happen as some jobs runs only once a day. I wrote this small JSP that exactly allows to do the same.

Here is the sample code for jsp for googlers like me
<%@page import="org.quartz.ee.servlet.QuartzInitializerServlet" %>
<%@page import="org.quartz.impl.StdSchedulerFactory" %>
<%@page import="org.quartz.*" %>
<%@page import="java.util.*" %>
<%
    String jobNameToRun=request.getParameter("jobNameToRun");
    String groupNameToRun=request.getParameter("groupNameToRun");
    String btnTrigger=request.getParameter("btnTrigger");
    StdSchedulerFactory factory = (StdSchedulerFactory)  pageContext.getServletContext().getAttribute(QuartzInitializerServlet.QUARTZ_FACTORY_KEY);
    Scheduler scheduler = factory.getScheduler();
    if("Trigger Now".equals(btnTrigger)) {
         scheduler.triggerJob(jobNameToRun, groupNameToRun);
%>
    Job <%=jobNameToRun%> triggered.<BR>
<%
    }

    for(String groupName : scheduler.getJobGroupNames()) {
%>
    <p>GroupName:<%=groupName%></p><br>
    <table border="1">
    <tr><td><b>JobName</b></td><td><b>Next Fire Time</b></td><td>&nbsp;</td></tr>
<%
        for(String jobName : scheduler.getJobNames(groupName)) {
            Trigger[] triggers = scheduler.getTriggersOfJob(jobName, groupName);
            Date nextFireTime = triggers[0].getNextFireTime();
%>      
        <tr><td><%=jobName%></td><td><%=nextFireTime%></td><td><form><input type="hidden" name="groupNameToRun" value="<%=groupName%>"/><input type="hidden" name="jobNameToRun" value="<%=jobName%>"/><input type="submit" name="btnTrigger" value="Trigger Now"/></form></tr>
<%      }
%>
    </table>
<%
    }
%>

Comments

  1. Thanks a lot for providing this incredibly precious post

    ReplyDelete
  2. dude you save my life

    ReplyDelete
  3. This is really a very very very precious post.. Thanks a ton the author...:)

    ReplyDelete
  4. Dude, Did you work in hibbert group anytime?

    ReplyDelete
  5. Hi can you provide the source for this example? Thanks!

    ReplyDelete
  6. Alberto the code pasted above is the source code of the example.

    ReplyDelete
  7. It is realy helpful to learn the idea.

    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…

What a rocky start to labor day weekend

Woke up by earthquake at 7:00 AM in morning and then couldn't get to sleep. I took a bath, made my tea and started checking emails and saw that after last night deployment three storage node out of 100s of nodes were running into Full GC. What was special about the 3 nodes was that each one was in a different Data centre but it was named same app02.  This got me curious I asked the node to be taken out of rotation and take a heap dump.  Yesterday night a new release has happened and I had upgraded spymemcached library version as new relic now natively supports instrumentation on it so it was a suspect. And the hunch was a bullseye, the heap dump clearly showed it taking 1.3G and full GCs were taking 6 sec but not claiming anything.



I have a quartz job in each jvm that takes a thread dump every 5 minutes and saves last 300 of them, checking few of them quickly showed a common thread among all 3 data centres. It seems there was a long running job that was trying to replicate pending…