Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
Description
If timers (here calendar timer) are running longer than scheduled, or the schedule/processing get stuck do to thread or cpu bottleneck, it is possible that the updates for persistence overlap.
The issue seems that the task(1) try to finish the timer and task(2) is about to start but see the concurrency.
The DB is updated with the 'old' next timeout, but the internal Timer instance will be updated with the next possible schedule due to a race condition between the two threads updating the object.
Attachments
Issue Links
- is cloned by
-
JBEAP-11519 [GSS](7.0.z) Race condition if timers overlap due to long running execution and short schedules if database persistence is used
- Verified