You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by "Richard C. L. Li (JIRA)" <ji...@codehaus.org> on 2006/01/24 04:26:06 UTC
[jira] Created: (CONTINUUM-569) Once CRON Expression Has Error,
Server Never Startup
Once CRON Expression Has Error, Server Never Startup
----------------------------------------------------
Key: CONTINUUM-569
URL: http://jira.codehaus.org/browse/CONTINUUM-569
Project: Continuum
Type: Bug
Versions: 1.0.2
Environment: SuSE Linux 9.2 AMD64
Reporter: Richard C. L. Li
Priority: Critical
To reproduce the problem:
1. Add a schedule with the following CRON expression:
0 0 4-1 * * ?
2. Restart the Continuum server.
3. The server never start up.
To workaround the problem:
1. Use JDBC to dig int he database and fix the CRON expression:
0 0 4-23 * * ?
2. Start the Continuum server.
3. Server starts successfully.
--
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] Commented: (CONTINUUM-569) Once CRON Expression Has Error,
Server Never Startup
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-569?page=comments#action_56744 ]
Emmanuel Venisse commented on CONTINUUM-569:
--------------------------------------------
Arghh, the cron expression validator from quartz is bad. I'll add more test in our own validator and will check that ranges are in correct order.
> Once CRON Expression Has Error, Server Never Startup
> ----------------------------------------------------
>
> Key: CONTINUUM-569
> URL: http://jira.codehaus.org/browse/CONTINUUM-569
> Project: Continuum
> Type: Bug
> Versions: 1.0.2
> Environment: SuSE Linux 9.2 AMD64
> Reporter: Richard C. L. Li
> Priority: Critical
>
>
> To reproduce the problem:
> 1. Add a schedule with the following CRON expression:
> 0 0 4-1 * * ?
> 2. Restart the Continuum server.
> 3. The server never start up.
> To workaround the problem:
> 1. Use JDBC to dig int he database and fix the CRON expression:
> 0 0 4-23 * * ?
> 2. Start the Continuum server.
> 3. Server starts successfully.
--
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] Commented: (CONTINUUM-569) Once CRON Expression Has Error,
Server Never Startup
Posted by "Richard C. L. Li (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-569?page=comments#action_56855 ]
Richard C. L. Li commented on CONTINUUM-569:
--------------------------------------------
Besides fixing the validator, I think codes in application startup should be fixed as well so that the application can staert up normally with invalid schedule disabled. Otherwise it is too hard for an administrator to fix the problem, since the broken schedule will completely bring down the web application and need to direct alter the databaase to change the schedule.
> Once CRON Expression Has Error, Server Never Startup
> ----------------------------------------------------
>
> Key: CONTINUUM-569
> URL: http://jira.codehaus.org/browse/CONTINUUM-569
> Project: Continuum
> Type: Bug
> Versions: 1.0.2
> Environment: SuSE Linux 9.2 AMD64
> Reporter: Richard C. L. Li
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 1.1-alpha-1
>
>
> To reproduce the problem:
> 1. Add a schedule with the following CRON expression:
> 0 0 4-1 * * ?
> 2. Restart the Continuum server.
> 3. The server never start up.
> To workaround the problem:
> 1. Use JDBC to dig int he database and fix the CRON expression:
> 0 0 4-23 * * ?
> 2. Start the Continuum server.
> 3. Server starts successfully.
--
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-569) Once CRON Expression Has Error,
Server Never Startup
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-569?page=all ]
Emmanuel Venisse updated CONTINUUM-569:
---------------------------------------
Assign To: Emmanuel Venisse
Fix Version: 1.1-alpha-1
> Once CRON Expression Has Error, Server Never Startup
> ----------------------------------------------------
>
> Key: CONTINUUM-569
> URL: http://jira.codehaus.org/browse/CONTINUUM-569
> Project: Continuum
> Type: Bug
> Versions: 1.0.2
> Environment: SuSE Linux 9.2 AMD64
> Reporter: Richard C. L. Li
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 1.1-alpha-1
>
>
> To reproduce the problem:
> 1. Add a schedule with the following CRON expression:
> 0 0 4-1 * * ?
> 2. Restart the Continuum server.
> 3. The server never start up.
> To workaround the problem:
> 1. Use JDBC to dig int he database and fix the CRON expression:
> 0 0 4-23 * * ?
> 2. Start the Continuum server.
> 3. Server starts successfully.
--
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-569) Once CRON Expression Has Error,
Server Never Startup
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-569?page=all ]
Emmanuel Venisse closed CONTINUUM-569:
--------------------------------------
Resolution: Fixed
Done.
> Once CRON Expression Has Error, Server Never Startup
> ----------------------------------------------------
>
> Key: CONTINUUM-569
> URL: http://jira.codehaus.org/browse/CONTINUUM-569
> Project: Continuum
> Type: Bug
> Versions: 1.0.2
> Environment: SuSE Linux 9.2 AMD64
> Reporter: Richard C. L. Li
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 1.0.3
> Attachments: continuum_stacktrace.log
>
>
> To reproduce the problem:
> 1. Add a schedule with the following CRON expression:
> 0 0 4-1 * * ?
> 2. Restart the Continuum server.
> 3. The server never start up.
> To workaround the problem:
> 1. Use JDBC to dig int he database and fix the CRON expression:
> 0 0 4-23 * * ?
> 2. Start the Continuum server.
> 3. Server starts successfully.
--
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-569) Once CRON Expression Has Error,
Server Never Startup
Posted by "Richard C. L. Li (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-569?page=all ]
Richard C. L. Li updated CONTINUUM-569:
---------------------------------------
Attachment: continuum_stacktrace.log
> Once CRON Expression Has Error, Server Never Startup
> ----------------------------------------------------
>
> Key: CONTINUUM-569
> URL: http://jira.codehaus.org/browse/CONTINUUM-569
> Project: Continuum
> Type: Bug
> Versions: 1.0.2
> Environment: SuSE Linux 9.2 AMD64
> Reporter: Richard C. L. Li
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 1.1-alpha-1
> Attachments: continuum_stacktrace.log
>
>
> To reproduce the problem:
> 1. Add a schedule with the following CRON expression:
> 0 0 4-1 * * ?
> 2. Restart the Continuum server.
> 3. The server never start up.
> To workaround the problem:
> 1. Use JDBC to dig int he database and fix the CRON expression:
> 0 0 4-23 * * ?
> 2. Start the Continuum server.
> 3. Server starts successfully.
--
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] Commented: (CONTINUUM-569) Once CRON Expression Has Error,
Server Never Startup
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-569?page=comments#action_56896 ]
Emmanuel Venisse commented on CONTINUUM-569:
--------------------------------------------
sure.
Can you attach stacktrace when continnuum can't start with a bad cron expression?
> Once CRON Expression Has Error, Server Never Startup
> ----------------------------------------------------
>
> Key: CONTINUUM-569
> URL: http://jira.codehaus.org/browse/CONTINUUM-569
> Project: Continuum
> Type: Bug
> Versions: 1.0.2
> Environment: SuSE Linux 9.2 AMD64
> Reporter: Richard C. L. Li
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 1.1-alpha-1
>
>
> To reproduce the problem:
> 1. Add a schedule with the following CRON expression:
> 0 0 4-1 * * ?
> 2. Restart the Continuum server.
> 3. The server never start up.
> To workaround the problem:
> 1. Use JDBC to dig int he database and fix the CRON expression:
> 0 0 4-23 * * ?
> 2. Start the Continuum server.
> 3. Server starts successfully.
--
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] Commented: (CONTINUUM-569) Once CRON Expression Has Error,
Server Never Startup
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-569?page=comments#action_56988 ]
Emmanuel Venisse commented on CONTINUUM-569:
--------------------------------------------
Fixed.
I'll close this issue when we'll use the new cron expression validator.
> Once CRON Expression Has Error, Server Never Startup
> ----------------------------------------------------
>
> Key: CONTINUUM-569
> URL: http://jira.codehaus.org/browse/CONTINUUM-569
> Project: Continuum
> Type: Bug
> Versions: 1.0.2
> Environment: SuSE Linux 9.2 AMD64
> Reporter: Richard C. L. Li
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 1.1-alpha-1
> Attachments: continuum_stacktrace.log
>
>
> To reproduce the problem:
> 1. Add a schedule with the following CRON expression:
> 0 0 4-1 * * ?
> 2. Restart the Continuum server.
> 3. The server never start up.
> To workaround the problem:
> 1. Use JDBC to dig int he database and fix the CRON expression:
> 0 0 4-23 * * ?
> 2. Start the Continuum server.
> 3. Server starts successfully.
--
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-569) Once CRON Expression Has Error,
Server Never Startup
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-569?page=all ]
John Casey updated CONTINUUM-569:
---------------------------------
Fix Version: (was: 1.1-alpha-1)
1.0.3
> Once CRON Expression Has Error, Server Never Startup
> ----------------------------------------------------
>
> Key: CONTINUUM-569
> URL: http://jira.codehaus.org/browse/CONTINUUM-569
> Project: Continuum
> Type: Bug
> Versions: 1.0.2
> Environment: SuSE Linux 9.2 AMD64
> Reporter: Richard C. L. Li
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 1.0.3
> Attachments: continuum_stacktrace.log
>
>
> To reproduce the problem:
> 1. Add a schedule with the following CRON expression:
> 0 0 4-1 * * ?
> 2. Restart the Continuum server.
> 3. The server never start up.
> To workaround the problem:
> 1. Use JDBC to dig int he database and fix the CRON expression:
> 0 0 4-23 * * ?
> 2. Start the Continuum server.
> 3. Server starts successfully.
--
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