Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

any idea why this happened?

same thing happened today also.

Thanks,
Ganesh.

Hi,

We are using Quartz-2.1.1 for Scheduling the jobs.
Job is running every 30 mins.
Around 6 hrs job was struck and it shown the below log message.
After 6 hrs it was automatically recovered and was running correctly

Logs:
Aug 21, 2014 7:07:02 AM org.quartz.impl.jdbcjobstore.JobStoreSupport recoverMisfiredJobs
INFO: Handling the first 20 triggers that missed their scheduled fire-time. More misfired triggers remain to be processed.
Aug 21, 2014 7:07:03 AM org.quartz.impl.jdbcjobstore.JobStoreSupport recoverMisfiredJobs
INFO: Handling 8 trigger(s) that missed their scheduled fire-time.

can someone please explain why this happened.

Thanks,
Ganesh G

Hi,

We are using Quartz-2.1.1 for Scheduling the jobs.
We observed that many Trigger Misfired Jobs happening in Production environment. And for next trigger time it was triggered correctly.
This happened once only.

Logs:
Aug 21, 2014 9:01:47 AM org.quartz.impl.jdbcjobstore.JobStoreSupport recoverMisfiredJobs
INFO: Handling 4 trigger(s) that missed their scheduled fire-time.
Aug 21, 2014 9:01:48 AM org.quartz.impl.jdbcjobstore.JobStoreSupport recoverMisfiredJobs
INFO: Handling 5 trigger(s) that missed their scheduled fire-time.

Aug 21, 2014 9:02:07 AM org.quartz.impl.jdbcjobstore.JobStoreSupport findFailedInstances
WARNING: This scheduler instance (FA11408531359971) is still active but was recovered by another instance in the cluster. This may cause inconsistent behavior.

can anyone please explain why this happened?

Thanks,
Ganesh

Hi,
Thanks for your reply. We have achieved that required functionality with given solution. But in Quartz Database the job previous_triggered_time and next_fire_time are not updating accordingly.
Please provide us is there any solution to achieve my requirement.

Thanks,
Ganesh

Hi All,

We are using quartz-all-2.1.1 version. using JDBC jobstore.We have few observations for scheduled jobs (ran from xml file)and triggered jobs (a scheduled job internally triggers this job)
Observation with scheduled job:
1). Same Quartz Job is running simultaneously.
means, one Job is running and before completion of this job same job trigger again because of that prevoius job is not completed within that interval time.
Observation with triggered job:
1). The same scenario gives a " org.quartz.ObjectAlreadyExistsException ".
Please provide explanation for above.

we want the same behaviour with scheudled jobs also i.e we dont want 2 instances of same job to run simultaneously.

Thanks,
Ganesh