|
If you were logged in you would be able to see more operations.
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
10 minutes
|
|
|
Remaining Estimate:
|
0 minutes
|
|
|
Time Spent:
|
10 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 ?
|
|
Description
|
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 ? |
Show » |
Sort Order:
|
Bug
Closed
Major
Trouble with bad entry in the cron's expression of a new schedule
Fixed.