[
https://issues.apache.org/jira/browse/AMQ-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004289#comment-13004289
]
Timothy Bish commented on AMQ-3199:
-----------------------------------
Ok, now I see what you are running into. Missed in the description that it was
the second time around that was causing the issue, think the extra 60 second
discussion confused me. I can fix the problem with the day being wrong but
having look more closely at the code I see where it can go wrong with other
crontab entries.
> CRON next scheduled time incorrectly calculated
> -----------------------------------------------
>
> Key: AMQ-3199
> URL: https://issues.apache.org/jira/browse/AMQ-3199
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.5.0
> Environment: Windows Server 2003 with java 1.6.0_22
> Reporter: Erik
> Assignee: Timothy Bish
> Fix For: 5.5.0
>
> Attachments: activemq-admin-query.txt, s1.png, s2.jpg
>
>
> A Cron Entry of "50 20 * * 5" with an AMQ_SCHEDULED_DELAY of 61000 (61
> seconds) started at 2011-03-04 20:48:24. The last "5" in the Cron Entry
> specifies only Fridays and 2011-03-04 is a Friday. The cron job ran and set
> "next scheduled time" to be 2011-03-10 20:50:25. 2011-03-11 is a Thursday.
> The correct "next scheduled time" should be 2011-03-11 20:50:25; it should be
> Friday.
> In addition, the reason why I set the delay to 61000 was because with the
> default delay of 0, the job executes twice with a 60 second interval. I will
> file a separate issue.
> I believe the Cron Entry has a problem with using asterisks. I tried a Cron
> Entry of "27 19 1-31 1-12 6" which is a Saturday. It ran at 19:27 and then
> correctly set the "next scheduled time" to be on the next Saturday. This is a
> temporary workaround.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
