Link to home
Create AccountLog in
Avatar of drazen_nikolic
drazen_nikolicFlag for Serbia

asked on

Quartz stops scheduling defined jobs

We are developing web application and using Spring 2.0.3 and Quartz 1.6.0 frameworks. For sometime now, we did not have any problems with Quartz scheduling the jobs. But, since recently, Quartz (integrated with Spring framework) which starts one job each 10 minutes, after few days just stops to starting this job. In the logs we have saw nothing except that before stopping scheduling this job, the last started job did not ever finished (we could not find the root cause of it).

Do you have any idea why is this happening, and is it possible to set the Quartz scheduler to run the job even if this job last time started did not ever finished its execution ?
Avatar of CEHJ
CEHJ
Flag of United Kingdom of Great Britain and Northern Ireland image

>>the last started job did not ever finished (we could not find the root cause of it).

Would the job be in any way dependent on the previous unfinished job?
Avatar of drazen_nikolic

ASKER

Hi CEHJ,

No, the next job does not depend on the previous (unfinished) job.
Post us :

1. The job code call, and the qualifications/dependencies for that call;
2. The job method's loop ( or routine ) terminating conditions and return type;
3. The disposal of the return type (if there was one) and the exception handler(s) for it if there are.

Remember to include any timers and scheduling parameters that you expect he code to follow.
There's not much point in guessing what's going on, so i think the first thing you need to do is to turn up Quartz' own logging to maximum verbosity
ASKER CERTIFIED SOLUTION
Avatar of Mick Barry
Mick Barry
Flag of Australia image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer