Trigger misfires

One Star

Trigger misfires

I'm running into a problem where I have X amount of tasks running on the same trigger execution time, but some of them are misfiring.
Let's take for example an Expected Trigger date of 03/23/2012 9:30.
I have 37 different tasks that are scheduled to run at this time.
Of those 37, only 18 executed OK.
expectedtriggeringdate basicstatus count
2012-03-23 09:30:00.000 MISFIRED 19
2012-03-23 09:30:00.000 OK 18
I believe this is directly related to the amount of threads defined in the file for the tomcat webapp.
Currently I have:
org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 20
org.quartz.threadPool.threadPriority = 5
org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread = true
1) Would increasing the org.quartz.threadPool.threadCount from 20 to 40 fix the misfiring?
2) Would I need to restart tomcat for these changes to take affect?
3) Is there anything else I can configure/change?

These misfirings are happening all the time.
One Star

Re: Trigger misfires

I changed the org.quartz.threadPool.threadCount to 40 and restarted Tomcat.
After an hour of monitoring, jobs no longer are misfiring.
A follow-up question I have is, eventually, 40 threadCount may not be enough. Can I put a value of 100?
One Star

Re: Trigger misfires

Hi Jebiya,
I am facing similar problem in TAC. Most of the jobs are showing Misfired. I am not sure why does it occur and what it means. I did change the thread count to 40 as you have mentioned, but has not resolved the issue yet. Any suggestion from your side?
Thank you.


Talend named a Leader.

Get your copy


Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

Best Practices for Using Context Variables with Talend – Part 1

Learn how to do cool things with Context Variables


Migrate Data from one Database to another with one Job using the Dynamic Schema

Find out how to migrate from one database to another using the Dynamic schema


Best Practices for Using Context Variables with Talend – Part 4

Pick up some tips and tricks with Context Variables