[
http://jira.codehaus.org/browse/CONTINUUM-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177207#action_177207
]
Wendy Smoak commented on CONTINUUM-2237:
----------------------------------------
While it would be great if Continuum could gracefully recover from a database
outage, at a minimum it needs to figure out that the database is gone and put
itself into a state where scheduled builds are suspended and users can't keep
pressing buttons.
I'd be happy if it simply displayed a page saying "Please contact your system
administrator" (while writing something useful in the log file).
> Better error handling and recovery from database outage
> -------------------------------------------------------
>
> Key: CONTINUUM-2237
> URL: http://jira.codehaus.org/browse/CONTINUUM-2237
> Project: Continuum
> Issue Type: Improvement
> Affects Versions: 1.3.2
> Reporter: Wendy Smoak
>
> Recently we had to re-start the server where Continuum's external MySQL
> database resides.
> We observed strange behavior in Continuum afterwards, including
> - 'invalid group id' when adding a project to an existing group, after it
> refreshed a few times on the 'in progress' page
> - "forgetting" that a user is logged in, in the middle of a release
> - redirecting to 'you are already logged in' when clicking on menu items
> - 'Error adding projects from modules' when adding a project to a group
> Re-starting Continuum seems to clear up the problems.
> Continuum needs to handle a database outage more gracefully.
--
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
