[ http://issues.apache.org/jira/browse/GERONIMO-2101?page=comments#action_12415688 ]
Aaron Mulder commented on GERONIMO-2101: ---------------------------------------- I've been trying service deployments lately, so I guess the same problem exists in the ServiceConfigBuilder. I don't have a specific failure procedure, I've just kind of noticed myself running into that a lot. I can try a few things to reproduce it. In the mean time, I'll attach a heavy-handed patch to Deployer, but if you can do something similar to 2078 for the ServiceConfigBuilder, that would be great. Thanks! > 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 > > 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
