continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wendy Smoak (JIRA)" <>
Subject [jira] Updated: (CONTINUUM-1743) Provide better error handling if DELETE of project fails
Date Wed, 09 Sep 2009 21:32:32 GMT


Wendy Smoak updated CONTINUUM-1743:

    Fix Version/s: Reviewed

> Provide better error handling if DELETE of project fails
> --------------------------------------------------------
>                 Key: CONTINUUM-1743
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>          Components: Database, Web - UI
>    Affects Versions: 1.1
>         Environment: Linux RedHat
>            Reporter: Andreas Guther
>             Fix For: Reviewed
> It appears that it is not possible to delete a project if it is in a certain state. 
The error message though is not very helpful:
> javax.jdo.JDOUserException: One or more instances could not be deleted
> NestedThrowables: javax.jdo.JDODataStoreException: Delete request
> NestedThrowables: SQL Exception: DELETE on table 'PROJECTDEPENDENCY'
> caused a violation of foreign key constraint 'PROJECT_FK2' for key (40580). The statement
has been rolled back.
> We had a process that seemed to be stuck.  We tried then to delete the project but this
only caused the error message above.  I believe that Continuum could not delete the project
because it was in a state that does not allow deleting it.  If this is the case I would like
to suggest to provide a better error handling letting the user know why the delete failed.
> We finally could delete the project after we restarted Continnum (not sure if this was
necessary, but that is what we did) and then building the project again.  This time it went
through and after the build was successful, we could delete the project.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message