-
Bug
-
Resolution: Done
-
Major
-
26.1.1.Final, 26.1.2.Final
After we upgrade Wildfly from 26.1.0 to 26.1.2, I found our cases not stable, sometimes the created timer will skipped and found below log:
01:24:42.976 DEBUG [org.jboss.as.ejb3.timer] (EJB default - 2) Timer is not active, skipping this scheduled execution at: Fri Sep 16 01:24:42 UTC 2022for [id=8c7ce6d9-351c-458e-8e49-ff938a5e8b96 timedObjectId=abcdefg auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@176cec24 previousRun=null initialExpiration=Fri Sep 16 01:24:42 UTC 2022 intervalDuration(in milli sec)=0 nextExpiration=Fri Sep 16 01:24:42 UTC 2022 timerState=ACTIVE info=abcdefg@2b937c98]
And from the release notes I found maybe below changes impact this timer logic.
https://github.com/wildfly/wildfly/pull/15463
Please double check it, thanks.
- is incorporated by
-
JBEAP-23981 [GSS](7.4.z) Created timer will random skipped due to "Timer is not active"
- Closed
- is related to
-
WFLY-16298 Improve performance related to TimerServiceImpl#scheduledTimerFutures
- Closed