石英触发器未触发

如何解决石英触发器未触发

我有一个在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,我的问题消失了,一切似乎都正常了。

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-