[ https://issues.apache.org/jira/browse/ARTEMIS-2926?focusedWorklogId=505690&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-505690 ]
ASF GitHub Bot logged work on ARTEMIS-2926: ------------------------------------------- Author: ASF GitHub Bot Created on: 28/Oct/20 11:27 Start Date: 28/Oct/20 11:27 Worklog Time Spent: 10m Work Description: franz1981 commented on pull request #3287: URL: https://github.com/apache/activemq-artemis/pull/3287#issuecomment-717871830 @clebertsuconic It seems that I was missing to correctly stop :) The CI now is green :+1: ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 505690) Time Spent: 3h 40m (was: 3.5h) > Scheduled task executions are skipped randomly > ---------------------------------------------- > > Key: ARTEMIS-2926 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2926 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker > Affects Versions: 2.13.0 > Reporter: Apache Dev > Assignee: Francesco Nigro > Priority: Major > Time Spent: 3h 40m > Remaining Estimate: 0h > > Scheduled tasks extending {{ActiveMQScheduledComponent}} could randomly skip > an execution, logging: > {code} > Execution ignored due to too many simultaneous executions, probably a > previous delayed execution > {code} > 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. -- This message was sent by Atlassian Jira (v8.3.4#803005)