Terracotta Discussion Forums

Hi !

We are using quartz 1.8.5. We have some problems with misfired jobs. One cron Trigger was scheduled at 19:00. But since 19:00 we get following messages over and over again:

Code:

 2011-05-31 19:01:25,804 INFO QuartzScheduler_Import Job Scheduler-NON_CLUSTERED_MisfireHandler - [quartz.LocalDataSourceJobStore] - Handling 1 trigger(s) that missed their scheduled fire-time.
 2011-05-31 19:01:25,831 INFO QuartzScheduler_Import Job Scheduler-NON_CLUSTERED_MisfireHandler - [history.LoggingTriggerHistoryPlugin] - Trigger wing.aa5c6266-fcb4-4e5b-9a0b-108351840846 misfired job wing.fakturierungJob  at:  19:01:25 05/31/2011.  Should have fired at:  19:00:00 05/31/2011
 2011-05-31 19:01:25,848 INFO QuartzScheduler_Import Job Scheduler-NON_CLUSTERED_MisfireHandler - [history.LoggingTriggerHistoryPlugin] - Trigger wing.aa5c6266-fcb4-4e5b-9a0b-108351840846 misfired job wing.fakturierungJob  at:  19:01:25 05/31/2011.  Should have fired at:  19:01:25 05/31/2011
 
 2011-05-31 19:03:25,880 INFO QuartzScheduler_Import Job Scheduler-NON_CLUSTERED_MisfireHandler - [quartz.LocalDataSourceJobStore] - Handling 1 trigger(s) that missed their scheduled fire-time.
 2011-05-31 19:03:25,954 INFO QuartzScheduler_Import Job Scheduler-NON_CLUSTERED_MisfireHandler - [history.LoggingTriggerHistoryPlugin] - Trigger wing.aa5c6266-fcb4-4e5b-9a0b-108351840846 misfired job wing.fakturierungJob  at:  19:03:25 05/31/2011.  Should have fired at:  19:01:25 05/31/2011
 2011-05-31 19:03:25,963 INFO QuartzScheduler_Import Job Scheduler-NON_CLUSTERED_MisfireHandler - [history.LoggingTriggerHistoryPlugin] - Trigger wing.aa5c6266-fcb4-4e5b-9a0b-108351840846 misfired job wing.fakturierungJob  at:  19:03:25 05/31/2011.  Should have fired at:  19:03:25 05/31/2011

I looks like the misfire handler does not manage to start the trigger immediately. He recognized again the trigger with the new fire time as a trigger that missed his fire-time.

Does anybody know what the problem is?

There must not be a worker thread available for executing the related job.

The SchedulerFactoryBean has no explicit taskExcecutor, so quartz will use his own threadpool. I don't think that there is no working thread available, because at schedule time the trigger was alone. There were no other triggers in execution.

Here is our SchedulerFactoryBean configuration.

Code:

 	<bean id="jobScheduler" class="org.springframework.scheduling.quartz.SchedulerFactoryBean">
 		<property name="dataSource" ref="dataSource"/>
 		<property name="schedulerName" value="Import Job Scheduler"/>
 		<property name="transactionManager" ref="transactionManager"/>
 		<property name="startupDelay" value="20" />
 		<property name="waitForJobsToCompleteOnShutdown" value="true" />
 		<property name="quartzProperties">
 			<props>
 				<!-- ThreadPool -->
 				<prop key="org.quartz.threadPool.class">org.quartz.simpl.SimpleThreadPool</prop>
 				<prop key="org.quartz.threadPool.threadCount">5</prop>
 				<prop key="org.quartz.threadPool.threadPriority">5</prop>
 				<!-- Job store -->
 				<prop key="org.quartz.jobStore.misfireThreshold">60000</prop>
 				<prop key="org.quartz.jobStore.driverDelegateClass">org.quartz.impl.jdbcjobstore.StdJDBCDelegate</prop>
 				<prop key="org.quartz.jobStore.lockHandler.class">org.quartz.impl.jdbcjobstore.SimpleSemaphore</prop>
 				<prop key="org.quartz.jobStore.useProperties">false</prop>
 				<prop key="org.quartz.jobStore.tablePrefix">QRTZ_</prop>
 				<prop key="org.quartz.jobStore.selectWithLockSQL">SELECT * FROM {0}LOCKS UPDLOCK WHERE LOCK_NAME = ?</prop>
 				<!-- Plugins -->
 				<prop key="org.quartz.plugin.shutdownhook.class">org.quartz.plugins.management.ShutdownHookPlugin</prop>
 				<prop key="org.quartz.plugin.shutdownhook.cleanShutdown">true</prop>
 				<prop key="org.quartz.plugin.triggHistory.class">org.quartz.plugins.history.LoggingTriggerHistoryPlugin</prop>
 				<prop key="org.quartz.plugin.triggHistory.triggerFiredMessage">Trigger {1}.{0} fired job {6}.{5} at: {4, date, HH:mm:ss MM/dd/yyyy}</prop>
 				<prop key="org.quartz.plugin.triggHistory.triggerCompleteMessage">Trigger {1}.{0} completed firing job {6}.{5} at {4, date, HH:mm:ss MM/dd/yyyy} with resulting trigger instruction code: {9}</prop>
 			</props>
 		</property>
 	</bean>