gpt4 book ai didi

quartz-scheduler - quartz 调度程序触发历史需要在触发后保存在数据库中

转载 作者:行者123 更新时间:2023-12-02 04:55:41 26 4
gpt4 key购买 nike

我正在使用 CronTriggerBean 和 SimpleTriggerBean quartz 调度程序来执行触发器。执行触发器后永久不保存有关触发器的详细信息。在执行之前触发器数据被存储在执行之后它被删除是什么问题。为此,我正在使用代码。

 <prop   key="org.quartz.plugin.triggHistory.class">org.quartz.plugins.history.LoggingTriggerHistoryPlugin</prop>    
<prop key="org.quartz.plugin.triggHistory.triggerFiredMessage">Trigger {1}.{0} fired job {6}.{5} at: {4, date, HH:mm:ss dd/MM/yyyy}</prop>
<prop key="org.quartz.plugin.triggHistory.triggerCompleteMessage">Trigger {1}.{0} completed firing job {6}.{5} at {4, date, HH:mm:ss dd/MM/yyyy} with resulting trigger instruction code: {9}</prop>
<prop key="org.quartz.plugin.triggHistory.triggerMisfiredMessage">Trigger [{1}.{0}] misfired job [{6}.{5}]. Should have fired at: {3, date, dd-MM-yyyy HH:mm:ss.SSS}</prop>
<prop key="org.quartz.plugin.jobHistory.class">org.quartz.plugins.history.LoggingJobHistoryPlugin</prop>
<prop key="org.quartz.plugin.jobHistory.jobToBeFiredMessage">Job [{1}.{0}] to be fired by trigger [{4}.{3}], re-fire: {7}</prop>
<prop key="org.quartz.plugin.jobHistory.jobSuccessMessage">Job {1}.{0} fired at: {2, date, dd/MM/yyyy HH:mm:ss} result=OK</prop>
<prop key="org.quartz.plugin.jobHistory.jobFailedMessage">Job {1}.{0} fired at: {2, date, dd/MM/yyyy HH:mm:ss} result=ERROR</prop>
<prop key="org.quartz.plugin.jobHistory.jobWasVetoedMessage">Job [{1}.{0}] was vetoed. It was to be fired by trigger [{4}.{3}] at: {2, date, dd-MM-yyyy HH:mm:ss.SSS}</prop>

最佳答案

您需要创建一个新的 pluginHistoty,它确实保存在 db 中并使用它代替 org.quartz.plugins.history。

LoggingInDbTriggerHistoryPlugin : ISchedulerPlugin, ITriggerListener
...

public virtualvoid TriggerComplete(..){
//save in db
}

关于quartz-scheduler - quartz 调度程序触发历史需要在触发后保存在数据库中,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/22573824/

26 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com