Quartz Scheduler suddenly stop running and no exception error?

If you are using a database to store jobs, check the trigger_state of your trigger. Right now I'm seeing a similar problem (or at least it has similar symptoms) A job that runs once a minute is leaving the trigger in "ACQUIRED" state and will never run again. Like you I'm seeing nothing the the log I'm also seeing a different cause of the same problem.

Again, the job just stops running, but the trigger is not in the "ACQUIRED" state. So far I don't know the cause What I know so far is that the scheduler thread is waiting for a free worker thread. It looks like all of the worker threads are waiting for a semaphore in order to update their schedule.

I haven't been able to get a thread dump yet to verify what the worker threads are waiting on I'm running Quartz 1.6.1 RC1. See this bug report: jira.opensymphony.com/browse/QUARTZ-668 I think that's what I'm seeing.

If you are using a database to store jobs, check the trigger_state of your trigger. Right now I'm seeing a similar problem (or at least it has similar symptoms). A job that runs once a minute is leaving the trigger in "ACQUIRED" state and will never run again.

Like you I'm seeing nothing the the log. I'm also seeing a different cause of the same problem. Again, the job just stops running, but the trigger is not in the "ACQUIRED" state.So far I don't know the cause.

What I know so far is that the scheduler thread is waiting for a free worker thread. It looks like all of the worker threads are waiting for a semaphore in order to update their schedule. I haven't been able to get a thread dump yet to verify what the worker threads are waiting on.

I'm running Quartz 1.6.1 RC1. See this bug report: jira.opensymphony.com/browse/QUARTZ-668 I think that's what I'm seeing.

Check if any Job is throwing an Exception. Put your Job exe code in a try catch block an trace any exception to troubleshoot the problem.

I had a similar problem but the problem was, I had 10 threads quartz default number of threads in quartz properties and when I made thread dump* I found that I have 10 jobs in blocked stat, which means that I can't run any more threads. A quick fix to this problem to increase the number of threads in the thread pool in the quartz properties. The actual fix was reviewing my code to know why I had a 10 blocked threads.

*to do thread dump you can use kill -3 which print the thread dump to your application standard output i. E if you running tomcat you find it in catalina. Out log file.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.