You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2006/04/29 03:00:37 UTC
[jira] Commented: (GERONIMO-1940) Bad deployment can't be
undeployed
[ http://issues.apache.org/jira/browse/GERONIMO-1940?page=comments#action_12377050 ]
Aaron Mulder commented on GERONIMO-1940:
----------------------------------------
Appears that no entry is written to config.xml, but the files are in the repository, and the uninstall command gives an error.
> Bad deployment can't be undeployed
> ----------------------------------
>
> Key: GERONIMO-1940
> URL: http://issues.apache.org/jira/browse/GERONIMO-1940
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment
> Versions: 1.1
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: db-plan-no-deps.xml
>
> If you deploy something that can't start, so it ends up in a not-started-but-not-stopped state (failed? starting?) then you can't stop or undeploy it and you're kind of stuck. For example, try deploying the attached database plan.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira