可以设置“集群” Quartz 设置的属性会导致单台机器出现问题吗？

发布于 2025-01-01 11:30:06 字数 1120 浏览 1 评论 0原文

我们配置了一堆quartz作业在集群环境中运行，并且在真实集群（两台WAS机器）上一切似乎都运行良好。

在DEV环境中我们仍然使用

org.quartz.jobStore.isClustered = true

虽然我们只使用单机。但我们经常但并不总是遇到以下异常：

org.quartz.JobPersistenceException: 
    Couldn't store trigger 'DEFAULT.MT_6uclr3emepk6p' for '<group>.<name>' 
    job:The job (<group>.<name>) referenced by the trigger does not exist.

我们将 DEV 环境的设置更改为

org.quartz.jobStore.isClustered = false

这似乎使问题消失了。

所以问题是：

当您实际上没有使用集群时，设置 org.quartz.jobStore.isClustered = true 是否有问题，
如果是的话，为什么？
如果不是，最初问题的原因可能是什么？

更新：澄清错误何时发生：

这是设置作业的代码片段。

JobKey JOBKEY = new JobKey("Name", "group");
newTrigger().withIdentity("TriggerName", "group").forJob(
                JOBKEY).build();
JobDetail job = newJob(NameJob.class).withIdentity(
                JOBKEY)
                .storeDurably().build();
scheduler.addJob(job, false);

该片段应该触发作业执行

scheduler.triggerJob(JOBKEY);

原文

We have a bunch of quartz jobs configured for running in a clustered environment and everything seems to work fine on the real cluster (two WAS machines).

In the DEV environment we still used

org.quartz.jobStore.isClustered = true

although we only use a single machine. But we get often but not always the following exception:

org.quartz.JobPersistenceException: 
    Couldn't store trigger 'DEFAULT.MT_6uclr3emepk6p' for '<group>.<name>' 
    job:The job (<group>.<name>) referenced by the trigger does not exist.

We changed the setup for the DEV environment to

org.quartz.jobStore.isClustered = false

This seemed to make the problem go away.

So the questions are:

Is it a problem to set org.quartz.jobStore.isClustered = true when you aren't actually using a cluster
if so why?
if not what might be the reason for the original problem?

UPDATE: Clarification on when the error occurs:

This is the snippet that sets up the job.

JobKey JOBKEY = new JobKey("Name", "group");
newTrigger().withIdentity("TriggerName", "group").forJob(
                JOBKEY).build();
JobDetail job = newJob(NameJob.class).withIdentity(
                JOBKEY)
                .storeDurably().build();
scheduler.addJob(job, false);

This snippet is supposed to trigger a job execution