<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Trigger misfires in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Trigger-misfires/m-p/2361672#M125976</link>
    <description>Update: 
&lt;BR /&gt;I changed the org.quartz.threadPool.threadCount to 40 and restarted Tomcat. 
&lt;BR /&gt;After an hour of monitoring, jobs no longer are misfiring. 
&lt;BR /&gt;A follow-up question I have is, eventually, 40 threadCount may not be enough. Can I put a value of 100?</description>
    <pubDate>Fri, 23 Mar 2012 21:27:19 GMT</pubDate>
    <dc:creator>jebiya</dc:creator>
    <dc:date>2012-03-23T21:27:19Z</dc:date>
    <item>
      <title>Trigger misfires</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Trigger-misfires/m-p/2361671#M125975</link>
      <description>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. 
&lt;BR /&gt;Let's take for example an Expected Trigger date of 03/23/2012 9:30. 
&lt;BR /&gt;I have 37 different tasks that are scheduled to run at this time. 
&lt;BR /&gt;Of those 37, only 18 executed OK. 
&lt;BR /&gt;expectedtriggeringdate basicstatus count 
&lt;BR /&gt;2012-03-23 09:30:00.000 MISFIRED 19 
&lt;BR /&gt;2012-03-23 09:30:00.000 OK 18 
&lt;BR /&gt;I believe this is directly related to the amount of threads defined in the quartz.properties file for the tomcat webapp. 
&lt;BR /&gt;Currently I have: 
&lt;BR /&gt;org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool 
&lt;BR /&gt;org.quartz.threadPool.threadCount = 20 
&lt;BR /&gt;org.quartz.threadPool.threadPriority = 5 
&lt;BR /&gt;org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread = true 
&lt;BR /&gt;1) Would increasing the org.quartz.threadPool.threadCount from 20 to 40 fix the misfiring? 
&lt;BR /&gt;2) Would I need to restart tomcat for these changes to take affect? 
&lt;BR /&gt;3) Is there anything else I can configure/change? 
&lt;BR /&gt; 
&lt;BR /&gt;These misfirings are happening all the time.</description>
      <pubDate>Fri, 23 Mar 2012 18:08:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Trigger-misfires/m-p/2361671#M125975</guid>
      <dc:creator>jebiya</dc:creator>
      <dc:date>2012-03-23T18:08:37Z</dc:date>
    </item>
    <item>
      <title>Re: Trigger misfires</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Trigger-misfires/m-p/2361672#M125976</link>
      <description>Update: 
&lt;BR /&gt;I changed the org.quartz.threadPool.threadCount to 40 and restarted Tomcat. 
&lt;BR /&gt;After an hour of monitoring, jobs no longer are misfiring. 
&lt;BR /&gt;A follow-up question I have is, eventually, 40 threadCount may not be enough. Can I put a value of 100?</description>
      <pubDate>Fri, 23 Mar 2012 21:27:19 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Trigger-misfires/m-p/2361672#M125976</guid>
      <dc:creator>jebiya</dc:creator>
      <dc:date>2012-03-23T21:27:19Z</dc:date>
    </item>
    <item>
      <title>Re: Trigger misfires</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Trigger-misfires/m-p/2361673#M125977</link>
      <description>Hi Jebiya,
&lt;BR /&gt;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?
&lt;BR /&gt;Thank you.</description>
      <pubDate>Mon, 07 May 2012 06:16:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Trigger-misfires/m-p/2361673#M125977</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2012-05-07T06:16:04Z</dc:date>
    </item>
  </channel>
</rss>

