Latest posts for the topic "getTriggersOfJob() reports wrong fire time when using TerracottaJobStore"

getTriggersOfJob() reports wrong fire time when using TerracottaJobStore

ciaranw — GMT

Hi, I'm currently evaluating Quartz coupled with the Terracotta Job store so it can be used across a cluster. I have knocked up a small webapp that will let you view jobs and their triggers. The problem I am having is that when I get the Trigger back for the Job, the previousFireTime and nextFireTime values are not the same for all schedulers in the cluster. The docs do not mention these methods being cluster-unaware, and a quick look at the source code suggests that the Trigger is retrieved straight from the JobStore. Having a look in the Terracotta dev console shows that the Triggers are serialised when they are put into the JobStore. Could this be anything to do with it? FYI, my quartz.properties is as follows: Code:

org.quartz.scheduler.instanceName = MyScheduler
org.quartz.scheduler.instanceId = AUTO
org.quartz.scheduler.rmi.export = false
org.quartz.scheduler.rmi.proxy = false

org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 3

org.quartz.jobStore.class = org.terracotta.quartz.TerracottaJobStore

org.quartz.jobStore.tcConfigUrl = localhost:9510

#===================================================
# Configure the Job Initialization Plugin
#===================================================

org.quartz.plugin.jobInitializer.class = org.quartz.plugins.xml.JobInitializationPlugin
org.quartz.plugin.jobInitializer.fileNames = META-INF/jobs.xml
org.quartz.plugin.jobInitializer.failOnFileNotFound = true
org.quartz.plugin.jobInitializer.wrapInUserTransaction = false

Cheers Ciaran

Re:getTriggersOfJob() reports wrong fire time when using TerracottaJobStore

teck — GMT

That is an interesting question that I don't immediately know the answer to. I could believe that the serialization is to blame for being able to observe the trigger fields in a stale state. We only force the local trigger state to be deserialized when the scheduler is actually acquiring the trigger. Sounds like we might need to do that if triggers are looked up for some other means. One thing to note is that there were some serious bugs in the terracotta job store before the 3.2.1 release. If you haven't already got the new version I recommend getting it before doing any more testing. Any chance you could put together a sample and the steps to run it to reproduce this problem?

Re:getTriggersOfJob() reports wrong fire time when using TerracottaJobStore

ciaranw — GMT

Hi, Sorry for the late reply, been very busy! I have put together a simple app that has two jobs scheduled that execute every 10 secs. All they do is log to the console. The webapp also contains a jsp that displays the last fired time and next fire time of the trigger for each job. The project uses maven, run it with mvn tc:run and it will boot up all the terracotta stuff and two instances of jetty. Go to http://localhost:8080/scheduler/index and http://localhost:8081/scheduler/index and you'll see that the times are not in sync. Cheers Ciaran

Re:getTriggersOfJob() reports wrong fire time when using TerracottaJobStore

gkeim — GMT

How about your tc-config.xml?

Re:getTriggersOfJob() reports wrong fire time when using TerracottaJobStore

ciaranw — GMT

gkeim wrote:

How about your tc-config.xml?

Not much different than a standard tc-config.xml: Code:





  
  
    
    
      %(user.home)/terracotta/server-data
      %(user.home)/terracotta/server-logs
    
  
    
  
    %(user.home)/terracotta/client-logs

Ciaran

Re:getTriggersOfJob() reports wrong fire time when using TerracottaJobStore

jayhogan — GMT

Has any progress been made on this issue? I could not find an open or closed bug in Jira related to this issue.

Re:getTriggersOfJob() reports wrong fire time when using TerracottaJobStore

ciaranw — GMT

jayhogan wrote:

Has any progress been made on this issue? I could not find an open or closed bug in Jira related to this issue.

Hi, It looks like it was fixed in the 3.2.1_2 release of terracotta, although I could not find any JIRA issues related to it. Upgrading to that version of terracotta (and related quartz, which i think was 1.8.1?) seemed to fix my problem. Ciaran