Description
EJB Timer WFLYEJB0043: A previous execution of timer ... when slow server start
When starting the JBoss instance with an EJB timer for example below, it looks like the application with the timer may be initialized but cannot start because the server has not stabilized and once JBoss is stabilized logs WFLYEJB0043 even though the timer was not previously (or should not have been previously running).
@Schedule(second="*/10", minute="*", hour="*", persistent=false) public void timeout() { log.info("Timer fired at 10 sec interval"); }
23:10:18,826 WARN [org.jboss.as.ejb3.timer] (EJB default - 2) WFLYEJB0043: A previous execution of timer [id=b8479e73-3d7a-4f88-8ac5-d0a0fd36194d timedObjectId=schedule-timer-not-persistent.schedule-timer-not-persistent.ScheduleSingleton auto-timer?:true persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@9803734 initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Wed Apr 10 23:10:10 CDT 2019 timerState=IN_TIMEOUT info=null] is still in progress, skipping this overlapping scheduled execution at: Wed Apr 10 23:10:18 CDT 2019.
Attachments
Issue Links
- relates to
-
AS7-3119 Recurring timer might executed concurrent if the duration of the timeout method will be longer than the interval
-
- Resolved
-
