You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org> on 2007/02/06 21:59:44 UTC

[jira] Updated: (CONTINUUM-320) Trouble with bad entry in the cron's expression of a new schedule

     [ http://jira.codehaus.org/browse/CONTINUUM-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Venisse updated CONTINUUM-320:
---------------------------------------

    Comment: was deleted

> Trouble with bad entry in the cron's expression of a new schedule
> -----------------------------------------------------------------
>
>                 Key: CONTINUUM-320
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-320
>             Project: Continuum
>          Issue Type: Bug
>          Components: Core system
>    Affects Versions: 1.0-alpha-4
>            Reporter: Emmanuel Venisse
>         Assigned To: Emmanuel Venisse
>             Fix For: 1.0-beta-1
>
>   Original Estimate: 10 minutes
>          Time Spent: 10 minutes
>  Remaining Estimate: 0 minutes
>
> From Olivier Lamy:
> I have encountered a trouble by setting a bad cron expression for a new
> scheduler : 0 0 0,4,8,12,16,20 * * * instead of 0 0 0,4,8,12,16,20 * * ?
> The continuum application fails and stop.
> Then it's was impossible to restart the application (always failed
> during the startup).
> The only solution to delete and install again the application.
> I found this issue http://jira.codehaus.org/browse/CONTINUUM-304.
> It's probably difficult to write an good validator. But is it possible
> to correctly catch the exception ?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira