You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org> on 2005/09/26 18:26:10 UTC
[jira] Created: (CONTINUUM-320) Trouble with bad entry in the cron's expression of a new schedule
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
Type: Bug
Components: continuum-core
Reporter: Emmanuel Venisse
>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
[jira] Closed: (CONTINUUM-320) Trouble with bad entry in the cron's expression of a new schedule
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-320?page=all ]
Emmanuel Venisse closed CONTINUUM-320:
--------------------------------------
Resolution: Fixed
Fixed.
> 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
> Type: Bug
> Components: continuum-core
> Versions: 1.0-alpha-4
> Reporter: Emmanuel Venisse
> Assignee: Emmanuel Venisse
> Fix For: 1.0-beta-1
>
> Original Estimate: 10 minutes
> Time Spent: 10 minutes
> Remaining: 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
[jira] Updated: (CONTINUUM-320) Trouble with bad entry in the cron's expression of a new schedule
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-320?page=all ]
Emmanuel Venisse updated CONTINUUM-320:
---------------------------------------
Assign To: Emmanuel Venisse
Version: 1.0-alpha-4
Fix Version: 1.0-beta-1
> 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
> Type: Bug
> Components: continuum-core
> Versions: 1.0-alpha-4
> Reporter: Emmanuel Venisse
> Assignee: Emmanuel Venisse
> Fix For: 1.0-beta-1
>
> Original Estimate: 10 minutes
> Time Spent: 10 minutes
> Remaining: 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