Latest posts for the topic "Misfire Instruction not working in quartz 1.8.3 using XML"

Misfire Instruction not working in quartz 1.8.3 using XML

bnchary — GMT

I am using the current xml file to trigger the jobs. But I'm not able to handle the misfires using this code. If I miss a firing because of the server shutdown, it should fire once the server is back on. The version of quartz is 1.8.3 and I cannot use the latest version where I can use the MISFIRE_INSTRUCTION_IGNORE_MISFIRE_POLICY in version 2.0 and higher to do the job. Is something wrong with the code ? I'm using the JDBCJobStore. Code:







    true
    false 




    
        NotificationJob
        MONTHLY_PGWEBSITE_JOBS
        something
        ClientNotificationJob
        false 
        false
        true
        
            
                notificationType
                BSEM
            
        
    

    
          
            billing_statements_email_trigger  
            MONTHLY_PGWEBSITE_TRIGGERS  
            clientBS_NotificationJob  
            MONTHLY_PGWEBSITE_JOBS
            false 
            MISFIRE_INSTRUCTION_FIRE_ONCE_NOW
            0 0 14 * * ?

I tried removing the tag, but did not work. Quartz-service.xml file Code:


		#============================================================================
		# Configure Main Scheduler Properties  
		#============================================================================

		org.quartz.scheduler.instanceName = MyQuartzSchedulerLOCAL
		org.quartz.scheduler.instanceId = AUTO
		org.quartz.scheduler.skipUpdateCheck = true
		
		#============================================================================
		# Configure ThreadPool  
		#============================================================================

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

		#============================================================================
		# Configure JobStore  
		#============================================================================

		org.quartz.jobStore.misfireThreshold = 60000

		org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX
		org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.MSSQLDelegate
		org.quartz.jobStore.useProperties = true

		org.quartz.jobStore.tablePrefix = QRTZ_
		org.quartz.jobStore.isClustered = true
		org.quartz.jobStore.clusterCheckinInterval = 20000

		#============================================================================
		# Configure Datasources  
		#============================================================================
		org.quartz.jobStore.dataSource = csBatch
		org.quartz.dataSource.csBatch.jndiURL = java:csBatchDS
     
		#============================================================================
		# Configure Plugins  
		#============================================================================
		
		org.quartz.plugin.jobInitializer.class = org.quartz.plugins.xml.XMLSchedulingDataProcessorPlugin
		org.quartz.plugin.jobInitializer.fileNames = batch_jobs.xml
		org.quartz.plugin.jobInitializer.failOnFileNotFound = true
		org.quartz.plugin.jobInitializer.wrapInUserTransaction = false

Re:Misfire Instruction not working in quartz 1.8.3 using XML

jhouse — GMT

So your schedule settings in question are: Code:

             MISFIRE_INSTRUCTION_FIRE_ONCE_NOW
             0 0 14 * * ?

This means fire every day at 2:00 PM. So you have tested the following way: Start the application before 2:00 PM, so that the xml file is read, and the trigger is added to the jobstore. Shut down the application before 2:00 PM. Leave the application down until after 2:00 PM + configured misfire threshold = 2:01 PM. Remove the XML file, or change these settings in the XML (to avoid error when it encounters the xml command to add a trigger that already exists, and to avoid it replacing the trigger with a new one that is therefore not misfired, because it didn't exist at 2:00 PM): change: Code:

 
     true
     false

to: Code:

 
     false
     true

Start the server, and see that the trigger scheduled before 2:00 PM for 2:00 PM fires now.

Re:Misfire Instruction not working in quartz 1.8.3 using XML

bnchary — GMT

Thanks for the prompt reply. Here is the scenario I have tested. I changed the cron trigger to fire every 10 min. I changed the Xml file as suggested, load the application, stop the server before firing time(suppose 3pm). Then when I have started the server at 3:05 pm, it is going to infinite loop as Code:

15:01:38,937 INFO  [StdSchedulerFactory] Quartz scheduler 'MyQuartzSchedulerLOCAL' initialized from an externally provided properties instance.
15:01:38,937 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.8.3
15:01:39,078 INFO  [JobStoreTX] ClusterManager: detected 1 failed or restarted instances.
15:01:39,078 INFO  [JobStoreTX] ClusterManager: Scanning for instance "0WS3016801323208730375"'s failed in-progress jobs.
15:01:39,140 INFO  [JobStoreTX] Handling 1 trigger(s) that missed their scheduled fire-time.
15:01:39,140 INFO  [XMLSchedulingDataProcessor] Parsing XML file: batch_jobs.xml with systemId: batch_jobs.xml
15:01:39,281 INFO  [XMLSchedulingDataProcessor] Adding 1 jobs, 1 triggers.
15:01:39,296 INFO  [XMLSchedulingDataProcessor] Not overwriting existing job: MONTHLY_PGWEBSITE_JOBS.clientBS_NotificationJob
15:01:39,296 INFO  [XMLSchedulingDataProcessor] Not overwriting existing trigger: MONTHLY_PGWEBSITE_TRIGGERS.billing_statements_email_trigger
15:01:39,312 INFO  [XMLSchedulingDataProcessor] Not overwriting existing trigger: MONTHLY_PGWEBSITE_TRIGGERS.billing_statements_email_trigger
15:01:39,312 INFO  [XMLSchedulingDataProcessor] Not overwriting existing trigger: MONTHLY_PGWEBSITE_TRIGGERS.billing_statements_email_trigger
15:01:39,328 INFO  [XMLSchedulingDataProcessor] Not overwriting existing trigger: MONTHLY_PGWEBSITE_TRIGGERS.billing_statements_email_trigger
15:01:39,328 INFO  [XMLSchedulingDataProcessor] Not overwriting existing trigger: MONTHLY_PGWEBSITE_TRIGGERS.billing_statements_email_trigger
15:01:39,343 INFO  [XMLSchedulingDataProcessor] Not overwriting existing trigger: MONTHLY_PGWEBSITE_TRIGGERS.billing_statements_email_trigger
15:01:39,343 INFO  [XMLSchedulingDataProcessor] Not overwriting existing trigger: MONTHLY_PGWEBSITE_TRIGGERS.billing_statements_email_trigger
15:01:39,359 INFO  [XMLSchedulingDataProcessor] Not overwriting existing trigger: MONTHLY_PGWEBSITE_TRIGGERS.billing_statements_email_trigger
15:01:39,359 INFO  [XMLSchedulingDataProcessor] Not overwriting existing trigger: MONTHLY_PGWEBSITE_TRIGGERS.billing_statements_email_trigger
15:01:39,375 INFO  [XMLSchedulingDataProcessor] Not overwriting existing trigger: MONTHLY_PGWEBSITE_TRIGGERS.billing_statements_email_trigger
15:01:39,375 INFO  [XMLSchedulingDataProcessor] Not overwriting existing trigger: MONTHLY_PGWEBSITE_TRIGGERS.billing_statements_email_trigger
15:01:39,375 INFO  [XMLSchedulingDataProcessor] Not overwriting existing trigger: MONTHLY_PGWEBSITE_TRIGGERS.billing_statements_email_trigger
15:01:39,406 INFO  [XMLSchedulingDataProcessor] Not overwriting existing trigger: MONTHLY_PGWEBSITE_TRIGGERS.billing_statements_email_trigger
.........

Re:Misfire Instruction not working in quartz 1.8.3 using XML

light5 — GMT

Hello bnchary, The infinite loop problem you have seen here is a bug, and it's been fixed in 1.8.6, but it's not release yet. http://jira.terracotta.org/jira/browse/QTZ-187 This is already fixed in quartz-2.1.0 or higher though.

Misfire Instruction not working in quartz 1.8.3 using XML

DAG87001 — GMT

We are also getting same exception about recover batch job, I did the setting as below and it is working fine

false

true

But I have one question here, how to load updated job in DB, now we have set flag as false ,so it will never take the updated batch job like if there is any xml change for existing batch job. How to handle this?