WFLYEJB0043:计时器的先前执行仍在进行中,跳过此重叠的计划执行 [英] WFLYEJB0043:A previous execution of timer is still in progress,skipping this overlapping scheduled execution at

查看:85
本文介绍了WFLYEJB0043:计时器的先前执行仍在进行中,跳过此重叠的计划执行的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我使用的是jbpm 7.37版本.我们使用的是wildfly 14.0.部署war文件后,服​​务器异常给出以下错误:

I am using jbpm 7.37 verison.We are using wildfly 14.0. Server abnormally gives below error just after a deployment of war files :

WARN  [org.jboss.as.ejb3.timer] (EJB default - 2) WFLYEJB0043: A previous execution of timer [id=6
9baf0d9-60b4-4775-982b-bf525682df3d timedObjectId=business-central.business-central.FileSystemDeleteWorker auto-timer?:tru
e persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@1ed2f93a initialExpiration=null intervalD
uration(in milli sec)=0 nextExpiration=Thu Apr 08 03:48:00 UTC 2021 timerState=IN_TIMEOUT info=null] is still in progress,
 skipping this overlapping scheduled execution at: Thu Apr 08 03:58:24 UTC 2021.

此问题的可能根本原因是什么?如何解决这个问题?此问题多数发生在TEST环境中.请提供帮助.

What could be the possible root cause for this issue ? How to solve this issue ? This issue mostl occruing on TEST environment.Please help.

注意:我们已经制作了自定义的REST API,并将其部署在kie-server.war文件中.此问题导致我的kie-server.war文件无法进一步使用,因此我们的自定义api不可用,并且减少应用程序.这是我们面临的严重问题.请提供帮助.

推荐答案

部署正在JBoss进入启动状态之前的某个时间间隔上调度EJB计时器.由于JBoss在完成所有内容的部署之前一直处于挂起状态,因此计时器可以在允许之前启动,因此一旦JBoss进入启动状态,您将看到一些警告,表明计时器无法调用,因为JBoss尚未启动完成了所有部署.

The deployment is scheduling an EJB timer on an interval that expires before JBoss moves into the started state. Since JBoss is in a suspended state until it finishes deploying everything, the timer can look to fire before it is allowed, thus once JBoss moves into the started state, you will see some warnings indicating that the timer was unable to invoke because JBoss had not finished deploying everything.

因此这些警告可以忽略.

So these warnings can be ignored.

根本原因:EJB 3.2规范部分[13.4.3计时器到期和超时回调方法]中的一段与该主题有些相关:

Root Cause : EJB 3.2 spec section [13.4.3 Timer Expiration and Timeout Callback Method] has a paragraph somewhat related to this topic:

在发生容器崩溃或容器关闭的情况下,在容器重新启动之前的这段时间内,任何已终止的单事件持久性计时器都必须使相应的超时回调方法在重新启动时被调用.在间隔时间内过期的任何间隔持久性计时器或基于计划的持久性计时器都必须使相应的超时回调方法至少在重新启动后被调用一次.

In the event of a con-tainer crash or container shutdown, any single-event persistent timers that have expired during the inter- vening time before container restart must cause the corresponding timeout callback method to be invoked upon restart. Any interval persistent timers or schedule based persistent timers that have expired during the intervening time must cause the corresponding timeout callback method to be invoked at least once upon restart.

这篇关于WFLYEJB0043:计时器的先前执行仍在进行中,跳过此重叠的计划执行的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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