-
Bug
-
Resolution: Done
-
Major
-
None
-
None
When a timer is reloaded for the first time in other node there are no listeners attached to it causing this problem (only in cluster environments with db timers)
2020-04-15 16:43:57,733 WARN [org.jboss.as.ejb3.timer] (Timer-1) WFLYEJB0161: Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' (id=33170e5f-3b34-4503-8796-9b5e6871c074) from its persistent state: java.lang.NullPointerException
at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence$RefreshTask.run(DatabaseTimerPersistence.java:851)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
- is cloned by
-
JBEAP-19539 [GSS](7.3.z)Hung process instances and associated server.log WARN "Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' "
- Closed
- is related to
-
JBPM-9120 Hung process instances and associated server.log WARN "Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' "
- Resolved
-
WFLY-9631 "Failed to reinstate timer" warning is shown when creating large number of EJB timers
- Closed
-
WFLY-13438 Database Timers: instances sporadically fail to start in a cluster
- Open
- relates to
-
JBEAP-19518 [GSS](7.2.z) WFLY-13386 - Hung process instances and associated server.log WARN "Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' "
- Closed