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/06/10 05:20:29 UTC
[jira] Created: (GERONIMO-2101) Deployment failures prevent future
deployments
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
[jira] Updated: (GERONIMO-2101) Deployment failures prevent future
deployments
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2101?page=all ]
Aaron Mulder updated GERONIMO-2101:
-----------------------------------
Attachment: 2101-deployer-cleanup.patch
> 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
[jira] Commented: (GERONIMO-2101) Deployment failures prevent
future deployments
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Resolved: (GERONIMO-2101) Deployment failures prevent future
deployments
Posted by "Kevan Miller (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2101?page=all ]
Kevan Miller resolved GERONIMO-2101:
------------------------------------
Resolution: Fixed
Repository directory was created, but not deleted if an error occurred during deployment.
Fix applied to branches/1.1 (413386) and trunk (413387).
> 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
> Assignee: Kevan Miller
> 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
[jira] Commented: (GERONIMO-2101) Deployment failures prevent
future deployments
Posted by "Kevan Miller (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Assigned: (GERONIMO-2101) Deployment failures prevent future
deployments
Posted by "Kevan Miller (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2101?page=all ]
Kevan Miller reassigned GERONIMO-2101:
--------------------------------------
Assign To: Kevan Miller
> 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
> Assignee: Kevan Miller
> 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
[jira] Commented: (GERONIMO-2101) Deployment failures prevent
future deployments
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ 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