Scheduled tasks missing their 'fire-time'

Rhythmyx Technical Discussion
1

In a 6.7 implementation I’ve started seeing the following messages in my server.log file. It looks like all my tasks are being run, but this is a little concerning…

2010-05-06 11:21:50,434 INFO  [com.percussion.Aging Agent] Polling aging action at: Thu May 06 11:21:50 GMT 2010...
2010-05-06 11:22:01,414 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 9 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:23:01,402 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 2 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:24:01,389 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 9 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:25:01,378 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 2 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:26:01,366 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 9 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:27:01,355 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 2 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:28:01,344 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 9 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:29:01,331 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 2 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:30:01,320 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 9 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:31:01,308 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 2 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:31:50,458 INFO  [com.percussion.Aging Agent] Polling aging action at: Thu May 06 11:31:50 GMT 2010...
2010-05-06 11:32:01,295 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 9 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:33:01,283 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 2 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:34:01,271 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 9 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:35:01,258 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 2 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:36:01,247 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 9 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:37:01,235 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 2 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:38:01,222 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 9 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:39:01,211 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 2 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:40:01,199 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 9 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:41:01,187 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 2 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:41:50,482 INFO  [com.percussion.Aging Agent] Polling aging action at: Thu May 06 11:41:50 GMT 2010...
2010-05-06 11:42:01,176 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 9 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:43:01,179 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 5 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:44:01,151 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 6 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:45:01,140 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 5 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:46:01,128 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 6 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:47:01,116 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 5 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:48:01,104 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 6 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:49:01,742 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 11 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:51:01,734 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 11 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:51:50,506 INFO  [com.percussion.Aging Agent] Polling aging action at: Thu May 06 11:51:50 GMT 2010...
2010-05-06 11:53:01,710 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 11 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:55:01,685 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 11 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:57:01,662 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 11 trigger(s) that missed their scheduled fire-time.
2010-05-06 11:59:01,638 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 11 trigger(s) that missed their scheduled fire-time.
2010-05-06 12:01:01,613 INFO  [org.quartz.impl.jdbcjobstore.JobStoreTX] Handling 11 trigger(s) that missed their scheduled fire-time.
2010-05-06 12:01:50,530 INFO  [com.percussion.Aging Agent] Polling aging action at: Thu May 06 12:01:50 GMT 2010...

Any ideas?

2

The “miss fire” may caused by (unnecessary) high frequency of the scheduled tasks, and/or the available quartz threads are too small.

So, you may try the following, see if you can reduce the amount of “miss fire” message:

(1) reduce the frequency of the scheduled tasks by changing the “Cron Specification” property of the scheduled tasks.

(2) increase the quartz threads by increaing the “quartzThreadCount” property for “sys_beanConfiguration” bean (which is defined in $RhythmyxRoot/AppServer/server/rx/deploy/rxapp.ear/rxapp.war/WEB-INF/config/spring/server-beans.xml). You may need to contact tech support for this if you haven’t work with Spring bean file before).