受Quartz DisallowConcurrentExecution影响的作业会如何处理 [英] What happens to jobs affected by Quartz DisallowConcurrentExecution

查看:270
本文介绍了受Quartz DisallowConcurrentExecution影响的作业会如何处理的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

由于不允许注释而导致作业无法运行时,会发生什么情况。

What happens when a job does not run because of the disallow annotation.

当前正在运行的实例死亡后,它是否排队等待运行?
是重复的运行是否被扔掉了,再也不会被听到?

Is it queued to run after the currently running instance dies? Is that duplicate "run" of it just thrown away, never to be heard from again?

我已经尝试过在代码中进行测试,但是对

I've tried testing in code, but my inexperience with the language and library is causing some difficulty.

推荐答案

附加触发只是延迟了(就像没有工作线程可运行)它们),直到第一个实例完成。如果这样导致错过下一个触发时间的时间超过了调度程序配置的失火阈值,那么失火指令将应用于被阻止的触发器。

The additional firings are just delayed (as if no worker thread is available to run them) until the first instance completes. If that causes the next fire time to be missed by more than the scheduler's configured misfire threshold, then the misfire instruction will be applied to the trigger that was blocked.

这篇关于受Quartz DisallowConcurrentExecution影响的作业会如何处理的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆