Quartz JobStoreSupport recoverMisfiredJobs Handling 3 trigger(s) that missed their scheduled fire-time

Question

We have a quartz application that works well on other environments.

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.

Any ideas what may have caused it? I am sure it's not our code since it never went through any TaskHandlers.

[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.

Updated :

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?

Also the TRIGGERS table shows it never fired:

NEXT_FIRE_TIME	PREV_FIRE_TIME	PRIORITY	TRIGGER_STATE	TRIGGER_TYPE	START_TIME	END_TIME	CALENDAR_NAME	MISFIRE_INSTR
1405630189133	-1	5	WAITING	CRON	1405624813000	0		0
1405630189139	-1	5	WAITING	CRON	1405624813000	0		0
1405630215140	-1	5	WAITING	CRON	1405624813000	0		0
1405630189126	-1	5	WAITING	CRON	1405624813000	0		0

Answer 1

Handling x Trigger(s) that missed their scheduled fire-time

is primarily due to the thread pool being exhausted. Check if multiple instances of a job are in running state