You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2011/02/16 22:40:24 UTC

[jira] Resolved: (AMQ-3036) Scheduled message CRON strings not parsed correctly

     [ https://issues.apache.org/jira/browse/AMQ-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQ-3036.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 5.5.0
         Assignee: Timothy Bish

Verified the issue, patches applied.  Many thanks for the unit tests.  

> Scheduled message CRON strings not parsed correctly
> ---------------------------------------------------
>
>                 Key: AMQ-3036
>                 URL: https://issues.apache.org/jira/browse/AMQ-3036
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.2
>         Environment: Windows XP 32 bit
>            Reporter: Nik Gehring
>            Assignee: Timothy Bish
>             Fix For: 5.5.0
>
>         Attachments: activemq-core.patch
>
>
> I am trying to send a scheduled message using a AMQ_SCHEDULED_CRON string but it  is being scheduled for really bizarre times!
> This is caused by errors in the org.apache.activemq.broker.scheduler.CronParser.getNextScheduledTime(..) - patch attached including junits.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira