[
http://issues.apache.org/jira/browse/GERONIMO-2101?page=comments#action_12415692
]
Aaron Mulder commented on GERONIMO-2101:
----------------------------------------
OK, here's a specific example. If you deploy a service and there's a typo in
one of the dependencies, you get:
Error: Unable to distribute foo-1.0.jar: Unable to create
configuration for deployment
load of test/foo/1.0/car failed
Unable to resolve dependency asdf/asdf/1.0/jar
Then if you fix the dependency and deploy again, you get:
Error: Unable to distribute foo-1.0.jar:
org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException:
Configuration already exists: test/foo/1.0/car
Meanwhile undeploy says:
Error: foo does not appear to be a the name of a module available
on the selected server. Perhaps it has already been stopped or
undeployed? If you're trying to specify a TargetModuleID, use the
syntax TargetName|ModuleName instead. If you're not sure what's
running, try the list-modules command.
If you try to undeploy or redeploy, it says it doesn't exist, but if you try to
deploy, it says it already exists. Pretty bad. :)
> Deployment failures prevent future deployments
> ----------------------------------------------
>
> Key: GERONIMO-2101
> URL: http://issues.apache.org/jira/browse/GERONIMO-2101
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment
> Versions: 1.1
> Reporter: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: 2101-deployer-cleanup.patch
>
> If you deploy and there's an error, the next deploy attempt invariably gets:
> Error: Unable to distribute foo-1.0.jar:
> org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException:
> Configuration already exists: bar/foo/1.0/car
> In other words, the bad deployment was written into the repository but not
> deleted when the deployment failed, and is now blocking future deployments.
> The only solution seems to be to manually delete the offending directory from
> the repository.
--
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
