0 Replies Latest reply on Aug 4, 2016 3:35 PM by Roger Lee

    WildFly 10.0.0.Final ERROR [org.jboss.as.ejb3] (EJB default - 1) WFLYEJB0020: Error invoking timeout for timer:

    Roger Lee Apprentice

      WildFly 10.0.0.Final on Mac OS X, standalone.

       

      I've started to get this error from a Singleton Schedule bean:

       

      ERROR [org.jboss.as.ejb3] (EJB default - 1) WFLYEJB0020: Error invoking timeout for timer: [id=a38ad8a8-26bb-4584-baef-99bd064bf326 timedObjectId=NoHagl.NoHaglJAR.ScheduleSingletonBean auto-timer?:true persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@5a40fe8b initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Thu Aug 04 20:15:00 BST 2016 timerState=IN_TIMEOUT info=null]: javax.ejb.EJBTransactionRolledbackException: Transaction rolled back


      I've found this entry re a bug


      https://issues.jboss.org/browse/WFLY-5195


      Some said they fixed this by:


      I have fixed this by simply modifying the timer state back to active.

      There are still some issues with clustered timers though, that basically relate to failed task detection (e.g. if a node in the cluster goes away with a task in IN_TIMEOUT, then other cluster nodes will not pick up the task). This requires quite a bit of feature development that I think is outside the scope of EAP7.0. To workaround this we should recommend that nodes are always shut down using graceful shutdown, as this will prevent this occurring.

      How do I do this?

      Thanks.