Continuum

Trouble with bad entry in the cron's expression of a new schedule

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0-alpha-4
  • Fix Version/s: 1.0-beta-1
  • Component/s: Core system
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

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 ?

Activity

Hide
Emmanuel Venisse added a comment -

Fixed.

Show
Emmanuel Venisse added a comment - Fixed.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:

Time Tracking

Estimated:
10m
Original Estimate - 10 minutes
Remaining:
0m
Remaining Estimate - 0 minutes
Logged:
10m
Time Spent - 10 minutes