石英触发器未触发

问题描述

我有一个在Tomcat上运行的Java Web应用程序。 我正在使用Quartz 2.3.0 (已更新为2.3.2,仍然无法正常工作) 我正在使用Properties初始化石英,如下所示:

Properties properties = new Properties();
properties.put("org.quartz.scheduler.instanceName",hostname);
properties.put("org.quartz.scheduler.instanceId",hostname);
properties.put("org.quartz.threadPool.threadCount","5");
properties.put("org.quartz.jobStore.class","org.quartz.impl.jdbcjobstore.JobStoreTX");
properties.put("org.quartz.jobStore.isClustered","true");
properties.put("org.quartz.jobStore.misfireThreshold","600000");//until 10 minutes,dont count as a misfire
properties.put("org.quartz.jobStore.clusterCheckinInterval","100000");
properties.put("org.quartz.jobStore.driverDelegateClass","org.quartz.impl.jdbcjobstore.StdJDBCDelegate");
properties.put("org.quartz.jobStore.dataSource","QCP");
properties.put("org.quartz.dataSource.QCP.connectionProvider.class","mypackage.quartz.QuartzConnectionProvider");
properties.put("org.quartz.plugin.shutdownhook.class","org.quartz.plugins.management.ShutdownHookPlugin");//This plugin catches the event of the JVM terminating (such as upon a CRTL-C) and tells the scheuler to shutdown.
properties.put("org.quartz.plugin.shutdownhook.cleanShutdown","false");
properties.put("org.quartz.scheduler.skipUpdateCheck","true");

Scheduler quartzScheduler quartzScheduler = new StdSchedulerFactory(properties).getScheduler();     

quartzScheduler.start();

然后我添加工作:

JobDetail runnableDetail = JobBuilder.newJob(RunnableJob.class)
                .withIdentity("runnable_JOB","runnable")
                .storeDurably(true)
                .requestRecovery(false)
                .build();
quartzScheduler.addJob(runnableDetail,true);

,然后为它创建一个触发器,如下所示:

String uuid = UUID.randomUUID().toString();
Trigger trigg = TriggerBuilder.newTrigger()
                .withIdentity("runnable_TRIGGER_"+uuid,"runnable")
                .forJob("runnable_JOB","runnable")
                .withSchedule(SimpleScheduleBuilder.simpleSchedule().withMisfireHandlingInstructionFireNow().withRepeatCount(0))
                .startAt(DateBuilder.futureDate(startDelaySeconds,IntervalUnit.SECOND)) //startDelaySeconds is between 1-300
                .build();

quartzScheduler.scheduleJob(trigg);

这是我的RunnableJob班:

public class RunnableJob implements Job {
    @Override
    public void execute(JobExecutionContext context) throws JobExecutionException {
        try {
            //some code
        } catch (Exception e) {
            //log the exception
        };
    }
}

但是触发器永远不会触发,当我在MysqL数据库中看到QRTZ_TRIGGERS表时,我可以看到该触发器和作业已成功添加,但是当触发该触发器的正确​​时间时,我看到了几秒钟后NEXT_FIRE_TIME列就会改变。

我已经阅读this并检查了这些值:

quartzScheduler.isstarted();
quartzScheduler.isInStandbyMode();

分别是:truefalse,这意味着调度程序处于正确的状态,而我的Trigger的状态也是WAITING

奇怪的是,它在我的系统上运行正常,但是在生产系统上部署它时失败。

我的系统上有Windows 10,服务器上有CentosTomcat 9,我正在使用Java 14

更新: 经过一些更改(而不是创建触发器和作业的方式)之后,NEXT_FIRE_TIME并没有更新,我检查了catalina.out并充满了以下异常:

31-Aug-2020 11:04:56.986 INFO [QuartzScheduler_demo123.domain.co-demo123.domain.co_ClusterManager] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load [meta-inf/services/javax.naming.spi.InitialContextFactory]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
    java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [meta-inf/services/javax.naming.spi.InitialContextFactory]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
        at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1385)
        at org.apache.catalina.loader.WebappClassLoaderBase.findResources(WebappClassLoaderBase.java:985)
        at org.apache.catalina.loader.WebappClassLoaderBase.getResources(WebappClassLoaderBase.java:1086)
        at java.base/java.util.ServiceLoader$LazyClasspathLookupIterator.nextProviderClass(ServiceLoader.java:1197)
        at java.base/java.util.ServiceLoader$LazyClasspathLookupIterator.hasNextService(ServiceLoader.java:1222)
        at java.base/java.util.ServiceLoader$LazyClasspathLookupIterator.hasNext(ServiceLoader.java:1266)
        at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1301)
        at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1386)
        at java.naming/javax.naming.spi.NamingManager.getinitialContext(NamingManager.java:697)
        at java.naming/javax.naming.InitialContext.getDefaultinitCtx(InitialContext.java:305)
        at java.naming/javax.naming.InitialContext.init(InitialContext.java:236)
        at java.naming/javax.naming.InitialContext.<init>(InitialContext.java:184)
        at mypackage.quartz.QuartzConnectionProvider.getConnection(QuartzConnectionProvider.java:25)
        at org.quartz.utils.DBConnectionManager.getConnection(DBConnectionManager.java:108)
        at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:780)
        at org.quartz.impl.jdbcjobstore.JobStoreTX.getNonManagedTXConnection(JobStoreTX.java:71)
        at org.quartz.impl.jdbcjobstore.JobStoreSupport.doCheckin(JobStoreSupport.java:3307)
        at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.manage(JobStoreSupport.java:3920)
        at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.run(JobStoreSupport.java:3957)
- ClusterManager: Error managing cluster: Failed to obtain DB connection from data source 'QCP': java.lang.NoClassDefFoundError: java/lang/Thread
org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'QCP': java.lang.NoClassDefFoundError: java/lang/Thread [See nested exception: java.lang.NoClassDefFoundError: java/lang/Thread]
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:789)
    at org.quartz.impl.jdbcjobstore.JobStoreTX.getNonManagedTXConnection(JobStoreTX.java:71)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.doCheckin(JobStoreSupport.java:3307)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.manage(JobStoreSupport.java:3920)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.run(JobStoreSupport.java:3957)
Caused by: java.lang.NoClassDefFoundError: java/lang/Thread
    at mypackage.quartz.QuartzConnectionProvider.getConnection(QuartzConnectionProvider.java:25)
    at org.quartz.utils.DBConnectionManager.getConnection(DBConnectionManager.java:108)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:780)
    ... 4 more

重启tomcat服务器并不能解决问题。

更新2:

问题似乎出在我试图与之建立连接的数据源中。 我的tomcat实例是在server.xml文件中定义的,带有不同的<Host>标签 及其资源在<Context>标签中为我的应用程序的每个实例定义:

<Resource name="jdbc/MysqL/hamkelasi" auth="Container" type="javax.sql.DataSource"
    
    initialSize="1" maxTotal="50" maxIdle="1" 
    maxWaitMillis="20000" removeAbandonedOnBorrow="true" removeAbandonedTimeout="600"
    validationQuery="select Now();" timeBetweenevictionRunsMillis="1800000"

    username="user" password="pass" driverClassName="com.MysqL.jdbc.Driver"
    url="..."
    />

然后在我的ContextListener中实例化一个javax.naming.InitialContext,然后使用.lookup(poolLookupString)。我在这里尝试过通过缓存InitialContext或缓存数据源的不同方法,但是没有成功。

仍然,问题仅出在具有相同配置和相同库的生产服务器上。

启动QuartsScheduler并尝试从数据库获取连接时发生错误。服务器和应用程序都正常运行,只有石英失败,并显示一个非常奇怪的错误

java.lang.NoClassDefFoundError: java/lang/Thread

而且我只在我的一个应用程序(用于测试porpuses)上使用QuartzScheduler

解决方法

当石英作业线程接收到一个触发器时,它将锁定该行并更新其下一次触发时间,否则它将进入未触发状态。

如果您想深入研究代码并检查发生了什么 (https://github.com/quartz-scheduler/quartz/blob/master/quartz-core/src/main/java/org/quartz/impl/jdbcjobstore/JobStoreSupport.java#L2831

尝试为工作和触发器注册侦听器,并检查是否被侦听

http://www.quartz-scheduler.org/documentation/quartz-2.3.0/tutorials/tutorial-lesson-07.html

,

通过将MySQL连接器版本更新为8,并使用com.mysql.cj.jdbc.Driver,我的问题消失了,一切似乎都正常了。