views:

2117

answers:

7

I have some quartz job which was running everyday at 7pm. Suddenly it failed to run. I check my server.log and there are no exception thrown. Anyone have any idea what could be the issue?

Thanks in advance

+1  A: 

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: http://jira.opensymphony.com/browse/QUARTZ-668

I think that's what I'm seeing.

Jon Strayer
A: 

I have this problem when I run Quartz.NET with the InMemory data store. The first 7000 triggers might work well and then it stops with any errors.

Any idea of what this could be?

Thanks, Patrick

Patrick
A: 

Hi All, I am also facing the same problem. In my application I am having a scheduler which runs for every 2 minutes. It is working fine for one and half day. After that it got stopped /paused .If we restart our Jboss server it is working fine for another one and half day.(Some times without restarting the server also it started working).

I am not seeing any exception in log and it is some thing strange. I am not able to understand the root cause of this problem. Please suggest me some solution.

I am working with Spring + Quarts 1.6.5

Regards, Prabakar.

Prabakar
A: 

Hi All, I have this problem with Quartz 1.6.1 + Spring 2.5.6 in my appacation. It is working fine in my test environment, but it alway stop running in my production environment(Linux + mysql) and without any log info.

I have no idea about it.

ryan
A: 

Hey I´m having a similar trouble, with a scheduler that must to run the second day of every month at 4pm... I have the next cronExpression= 0 4 * 2 * ?

I've looked up in Quartz, and the expression seems to be fine. But the trigger is never fired. Only when I try with this one: 0 0/10 * * * ?

And I dont know why is happening this. I've worked with quartz before in Eclipse and works fine except this time that I'm using WebSphere 6.0.

I'm working with Spring and Quartz 1.6.5

If anyone has a clue of what´s happenning, please let me know.

Greetings and sorry for my bad english.

elizabeth
A: 

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.

juanjo.arana
A: 

Same problem here as well. I hope someone posts a solution to this, since I'm still investigating it. For me it happens roughly after 40 minutes of running tomcat. The last lines printed to the log are:

[org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-4] DEBUG JobRunShell - Calling execute on job DEFAULT.*job-name*

for each job (I have about 12).

Asaf Mesika