You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Nik Gehring (JIRA)" <ji...@apache.org> on 2010/11/15 11:23:24 UTC

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

Scheduled message CRON strings not parsed correctly
---------------------------------------------------

                 Key: AMQ-3036
                 URL: https://issues.apache.org/activemq/browse/AMQ-3036
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.5.0
         Environment: Windows XP 32 bit
            Reporter: Nik Gehring
         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.
-
You can reply to this email to add a comment to the issue online.


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

Posted by "Nik Gehring (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nik Gehring updated AMQ-3036:
-----------------------------

    Attachment: activemq-core.patch

patch file

> Scheduled message CRON strings not parsed correctly
> ---------------------------------------------------
>
>                 Key: AMQ-3036
>                 URL: https://issues.apache.org/activemq/browse/AMQ-3036
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.0
>         Environment: Windows XP 32 bit
>            Reporter: Nik Gehring
>         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.
-
You can reply to this email to add a comment to the issue online.