Hi all,
We've implemented quartz and everything was working fine till last night 3AM, Since 3AM no jobs start running. I could still schedule job and QRTZ tables get filled. but the jobs self won't execute when reaching the fire time. does any one has a clue why quartz stops executing while the rest of the application is just working fine. (Quartz version used is version 1.6.6, because this is the last version with java 1.4 support).
quartz.properties
Code:
#Quartz indentifiers
org.quartz.scheduler.instanceId=AUTO
org.quartz.scheduler.instanceName=SamedayScheduler
#Time to try to reconnect to the server when the database connection is lost.
org.quartz.scheduler.dbFailureRetryInterval=120000
#General settings
org.quartz.jobStore.class=org.quartz.impl.jdbcjobstore.JobStoreCMT
org.quartz.jobStore.dataSource=samedayDS
org.quartz.jobStore.nonManagedTXDataSource=nonXAsamedayDS
org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.oracle.OracleDelegate
org.quartz.jobStore.misfireThreshold=60000
org.quartz.jobStore.tablePrefix=sa_qrtz_
#Cluster settings
org.quartz.jobStore.isClustered=false
#org.quartz.jobStore.clusterCheckinInterval=20000
org.quartz.jobStore.dontSetAutoCommitFalse=true
#Thread settings
org.quartz.threadPool.class=org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount=5
#datasource settings
org.quartz.dataSource.samedayDS.jndiURL=jdbc/sday_ds_tx
org.quartz.dataSource.samedayDS.java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory
org.quartz.dataSource.samedayDS.java.naming.provider.url=iiop://localhost:2809
org.quartz.dataSource.nonXAsamedayDS.jndiURL=jdbc/sameday/oracle/BatchDS
org.quartz.dataSource.nonXAsamedayDS.java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory
org.quartz.dataSource.nonXAsamedayDS.java.naming.provider.url=iiop://localhost:2809
Edit: after restarting the server the jobs where start runnning again