geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevan Miller (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-2101) Deployment failures prevent future deployments
Date Sat, 10 Jun 2006 17:17:30 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-2101?page=comments#action_12415684 ] 

Kevan Miller commented on GERONIMO-2101:
----------------------------------------

Aaron, can you please provide a specific failure scenario? As is, it's impossible to tell
if this is or is not a problem and where the problem might be...

The problem I fixed was a problem with EAR deployments -- appclient configurations wouldn't
be cleaned up. This was the problem reported by 2078.

> 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


Mime
View raw message