[
https://issues.redhat.com/browse/WFLY-13542?page=com.atlassian.jira.plugi...
]
Cheng Fang commented on WFLY-13542:
-----------------------------------
I don't think this is a bug. See related issue AS7-3119 for detailed discussion. When
multiple executions of the same timer overlaps while the first exection is still running,
WildFly drops other overlapping executions of the same timer, to prevent over-flooding the
bean instance and also to avoid confusing users. After all, the purpose of a specific
timer is to do something at a certain time, which is already fulfilled by running the
first execution.
Container does not enforce bean-managed concurrency for timeout
methods
-----------------------------------------------------------------------
Key: WFLY-13542
URL:
https://issues.redhat.com/browse/WFLY-13542
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 19.1.0.Final
Reporter: Fábio Silva
Assignee: Cheng Fang
Priority: Major
Bean-managed concurrency for @Singleton EJBs is not enforced for timeout methods
annotated with @Schedule. When a timeout is fired while the previous one is still running,
the timeout method is not called. Instead, WildFly logs a warning like the following:
{code:java}
20:58:54,000 WARN [org.jboss.as.ejb3.timer] (EJB default - 2) WFLYEJB0043: A previous
execution of timer [id=aa716284-ef7b-4bb3-a356-a8ca187255c4
timedObjectId=myweb.myweb.MySingleton auto-timer?:true persistent?:false
timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@303bd2d5 previousRun=Sun May
31 20:57:10 BRT 2020 initialExpiration=null intervalDuration(in milli sec)=0
nextExpiration=Sun May 31 20:58:54 BRT 2020 timerState=IN_TIMEOUT info=null]
ScheduleExpression
[second=0/1;minute=*;hour=*;dayOfMonth=*;month=*;dayOfWeek=*;year=*;timezoneID=null;start=null;end=null]
is still in progress, skipping this overlapping scheduled execution at: Sun May 31
20:58:54 BRT 2020.
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)