<?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: QUARTZ trigger misfire configuration in Data Quality</title>
    <link>https://community.qlik.com/t5/Data-Quality/QUARTZ-trigger-misfire-configuration/m-p/2280928#M3586</link>
    <description>&lt;P&gt;Hi friariello,&lt;/P&gt;&lt;P&gt;I have seen your post ist pretty old, but still. Did you find a solution for your issue? I need a robust solution, when the jobserver is temporarily not available and would like to use the option:&amp;nbsp;&lt;SPAN&gt;MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_REMAINING_COUNT or similar.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you for your comments.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Tobi&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 15 May 2019 11:58:02 GMT</pubDate>
    <dc:creator>Tobi1</dc:creator>
    <dc:date>2019-05-15T11:58:02Z</dc:date>
    <item>
      <title>QUARTZ trigger misfire configuration</title>
      <link>https://community.qlik.com/t5/Data-Quality/QUARTZ-trigger-misfire-configuration/m-p/2280927#M3585</link>
      <description>Hi, 
&lt;BR /&gt;we're using Talend Data Quality Enterprise Edition V. 5.1.2, with TAC and Job conductor to deploy jobs and create triggers. 
&lt;BR /&gt;In our environment, we want to avoid misfiring triggers to fire jobs; 
&lt;BR /&gt;we are trying to reproduce the following behaviour: 
&lt;BR /&gt;1 - A simple trigger fires a job every X seconds; 
&lt;BR /&gt;2 - A job execution takes more than X seconds; 
&lt;BR /&gt;3 - The job has to start only at scheduled X seconds interval, with no running job's instance, and misfired triggers must be ignored 
&lt;BR /&gt;e.g. 
&lt;BR /&gt;trigger fires at: 
&lt;BR /&gt;00:00:30 
&lt;BR /&gt;00:01:00 
&lt;BR /&gt;00:01:30 
&lt;BR /&gt;00:02:00 
&lt;BR /&gt;... 
&lt;BR /&gt;Job is fired at 00:00:30 and takes 45 seconds to end. The 00:01:00 trigger has to be ignored and 
&lt;BR /&gt;next job execution must be scheduled at 00:01:30. 
&lt;BR /&gt;We would like to know: 
&lt;BR /&gt;- How we can configure this behaviour on a single SimpleTrigger; 
&lt;BR /&gt;- How we can configure this as default behaviour on Quartz properties file (into TAC//WEB-INF/classes). 
&lt;BR /&gt;We tried to reproduce a similar situation using org.quartz.jobStore.misfireThreshold, set to a low value; 
&lt;BR /&gt;we experienced that this value allow to reproduce this behaviour, but often, if it's too low, prevents other triggers on other jobs to be fired correctly. 
&lt;BR /&gt;We also found this instructions MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_EXISTING_COUNT and MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_REMAINING_COUNT, which can be set into a Quartz SimpleTrigger. 
&lt;BR /&gt;We would like to know if and how we can set this instructions while creating simpleTrigger into TAC, and if exist other similar instructions to be configured 
&lt;BR /&gt;into Quartz properties file. 
&lt;BR /&gt;Thanks</description>
      <pubDate>Sat, 16 Nov 2024 12:04:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Data-Quality/QUARTZ-trigger-misfire-configuration/m-p/2280927#M3585</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T12:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: QUARTZ trigger misfire configuration</title>
      <link>https://community.qlik.com/t5/Data-Quality/QUARTZ-trigger-misfire-configuration/m-p/2280928#M3586</link>
      <description>&lt;P&gt;Hi friariello,&lt;/P&gt;&lt;P&gt;I have seen your post ist pretty old, but still. Did you find a solution for your issue? I need a robust solution, when the jobserver is temporarily not available and would like to use the option:&amp;nbsp;&lt;SPAN&gt;MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_REMAINING_COUNT or similar.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you for your comments.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Tobi&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2019 11:58:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Data-Quality/QUARTZ-trigger-misfire-configuration/m-p/2280928#M3586</guid>
      <dc:creator>Tobi1</dc:creator>
      <dc:date>2019-05-15T11:58:02Z</dc:date>
    </item>
    <item>
      <title>Re: QUARTZ trigger misfire configuration</title>
      <link>https://community.qlik.com/t5/Data-Quality/QUARTZ-trigger-misfire-configuration/m-p/2280929#M3587</link>
      <description>&lt;P&gt;Hello , I have been also looking answer for this, Does anyone found any solution on this please ? &lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2022 19:17:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Data-Quality/QUARTZ-trigger-misfire-configuration/m-p/2280929#M3587</guid>
      <dc:creator>PPat9713</dc:creator>
      <dc:date>2022-03-10T19:17:04Z</dc:date>
    </item>
  </channel>
</rss>

