Timer stuck sporadically if a database persistence is used

Solution Verified - Updated -


  • For a persistent timer there are some messages like below that the timer is not executed due to overlap with an already running one, this works normally, but sometimes the timer is not longer active after this. We need to restart the server to get this fixed.
11:50:53,001 WARN  [org.jboss.as.ejb3.timer] (EJB default - 7) WFLYEJB0043: A previous execution of timer [id=0203e061-b8da-4349-bd93-7f5316d59d6d timedObjectId=ejb31-timer.ejb31-timer.SimpleScheduleSingletonTimerBean auto-timer?:true persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@58a23128 initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Wed Jun 14 11:50:53 CEST 2017 timerState=IN_TIMEOUT info=null] is still in progress, skipping this overlapping scheduled execution at: Wed Jun 14 11:50:53 CEST 2017.
  • Seeing occasional issue with a persistent scheduler job updating next_date column in jboss_ejb_timer database table with past date. This causes scheduler job to not run again.


  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.x
    • 7.0.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In