-
Bug
-
Resolution: Done
-
Critical
-
29.0.0.Alpha1
-
None
-
---
-
---
During cluster membership change, the DistributableTimerService reschedules timer execution based on changes in primary ownership. If a user concurrently invokes TimerService.getTimers() (or getAllTimers()), any timers in the process of being unscheduled on one member and reschedule elsewhere can be omitted from the resulting Collection<Timer>.
- relates to
-
JBEAP-24863 OpenShift - High frequency distributed timer fail-over is failing sometimes
- Closed
-
JBEAP-24975 OpenShift - Distributed Timers, timer not found by TimerService::getTimers sometimes
- Closed