Description
Scheduled tasks extending ActiveMQScheduledComponent could randomly skip an execution, logging:
Execution ignored due to too many simultaneous executions, probably a previous delayed execution
The problem is in the "ActiveMQScheduledComponent#runForExecutor" Runnable.
Times to be compared (currentTimeMillis() and lastTime) are taken inside the runnable execution itself. So, depending on relative execution times, it could happen that the difference is less than the given period (e.g. 1 ms), resulting in a skipped execution.
Attachments
Issue Links
- relates to
-
ARTEMIS-2916 Two servers becoming Live using JDBC Shared Store
- Resolved
- links to