title: Quartz JobStoreSupport recoverMisfiredJobs Handling 3 trigger(s) that missed their scheduled fire-time
body: <p>We have a quartz application that works well on other environments.</p>
  <p>But when we deployed it in a clustered environment with two needs, it stopped working. All I can see are tons of the log shown below.</p>
  <p>Any ideas what may have caused it? I am sure it's not our code since it never went through any TaskHandlers.</p>
  <pre><code>[7/17/14 13:14:54:236 EDT] 00000025 JobStoreTX    I org.quartz.impl.jdbcjobstore.JobStoreSupport recoverMisfiredJobs Handling 3 trigger(s) that missed their scheduled fire-time.
  </code></pre>
  <p><strong>Updated :</strong></p>
  <p>I'm suspecting it maybe due to the transaction isolation level configuration. Currently the quartz data source is configured to TRANSACTION_READ_COMMITTED (CS). Any suggestion on the appropriate value?</p>
  <p>Also the TRIGGERS table shows it never fired:</p>
  <div class="s-table-container">
  <table class="s-table">
  <thead>
  <tr>
  <th>NEXT_FIRE_TIME</th>
  <th>PREV_FIRE_TIME</th>
  <th>PRIORITY</th>
  <th>TRIGGER_STATE</th>
  <th>TRIGGER_TYPE</th>
  <th>START_TIME</th>
  <th>END_TIME</th>
  <th>CALENDAR_NAME</th>
  <th>MISFIRE_INSTR</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td>1405630189133</td>
  <td>-1</td>
  <td>5</td>
  <td>WAITING</td>
  <td>CRON</td>
  <td>1405624813000</td>
  <td>0</td>
  <td></td>
  <td>0</td>
  </tr>
  <tr>
  <td>1405630189139</td>
  <td>-1</td>
  <td>5</td>
  <td>WAITING</td>
  <td>CRON</td>
  <td>1405624813000</td>
  <td>0</td>
  <td></td>
  <td>0</td>
  </tr>
  <tr>
  <td>1405630215140</td>
  <td>-1</td>
  <td>5</td>
  <td>WAITING</td>
  <td>CRON</td>
  <td>1405624813000</td>
  <td>0</td>
  <td></td>
  <td>0</td>
  </tr>
  <tr>
  <td>1405630189126</td>
  <td>-1</td>
  <td>5</td>
  <td>WAITING</td>
  <td>CRON</td>
  <td>1405624813000</td>
  <td>0</td>
  <td></td>
  <td>0</td>
  </tr>
  </tbody>
  </table>
  </div>