You can look at var/config/config.xml, and see if there's an entry in
there for the application. If so you could remove it or add
load="false", but it sounds like maybe there's not an entry?
You can also find the files for the application in geronimo/repository
(in a subdirectory based on the application's module ID) and delete
them. That will make sure there's nothing "blocking" the new
deployment.
Thanks,
Aaron
On 2/8/07, Geronimo User <[EMAIL PROTECTED]> wrote:
Hi:
Is there a way to recover when Geronimo is confused about whether an
application is deployed. This follows a deployment that failed.
I've changed the deployment info and again try to deploy.
The list-modules command does not show the module.
But when I try to deploy, the command says the module does exist:
Error: Unable to distribute your-ear-m.n.ear:
org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException:
Configuration already exists: com.yourcompany/your-ear/m.n/ear
Is there a way to recover from this without re-installing Geronimo?
Thanks.
