This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have a Spring Quartz scheduler which is clustered on multipele servers. The quartz properties are loaded from spring context as follows :
Now, here is my problem. Sometimes the Cron trigger doesn't fire at all and i get the following error on my console:
2011-09-12 06:24:20,804 [QuartzScheduler_Quartz Scheduler-testserver.corp1315801853523_ClusterManager] WARN org.springframework.scheduling.quartz.LocalDataSourceJobStore - This scheduler instance (ORLLA001.curascript.root.corp1315801853523) is still active but was recovered by another instance in the cluster. This may cause inconsistent behavior.
What could be the reason for this? Is this something that could happen when more than 5 threads get triggered by quartz? (Since i hjave specified the threadCound as 5) ?
Thanks in advance for the help.
'Scientia est Potentia'
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Inconsistent behaviour by Spring Quartz Scheduler.