[
https://issues.apache.org/jira/browse/AMQ-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004180#comment-13004180
]
Erik edited comment on AMQ-3199 at 3/8/11 8:31 PM:
---------------------------------------------------
I downloaded the latest 5.5 snapshot and repeated the issue. The issue still
exists. I have attached two screen shots to show the problem.
s1.png shows the initial Cron Entry set to run Tuesday 3/8/2011 @ 12:11:35pm.
s2.png shows the Cron Entry after the message was delivered. The next scheduled
time is incorrectly set for 3/14/2011 @ 12:10:35pm which is Monday. It should
be set for 3/15/2011 @ 12:10:35pm; i.e. Tuesday.
The activemq version I downloaded was
apache-activemq-5.5-SNAPSHOT-bin-2011-03-06-03-55-16.zip.
was (Author: aletheia7):
I downloaded the latest 5.5 snapshot and repeated the issue. The issue
still exists. I have attached two screen shots to show the problem.
> 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: 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
