geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Delos Dai (JIRA)" <>
Subject [jira] Commented: (GERONIMODEVTOOLS-337) Configuration already exists exception
Date Wed, 09 Sep 2009 07:51:57 GMT


Delos Dai commented on GERONIMODEVTOOLS-337:

I think it's not just the problem of sync. If you deploy a module to G server without GEP,
it may also produce a "Configuration already exist" exception. I think it's due to the problem
of G server deployer. The exception is likely to be thrown  in deployment if there has been
a  deployment happened before and failed. So the best solution for this JIRA is to let G server
remove  the deployed modules once they're not deployed successfully.

So I suggest to find a scenario always producing the problem and report it to G server as
a JIRA. Then, this JIRA can be closed.

> Configuration already exists exception
> --------------------------------------
>                 Key: GERONIMODEVTOOLS-337
>                 URL:
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 2.1.0
>            Reporter: Tim McConnell
>            Assignee: Tim McConnell
>             Fix For: 2.2.0
> Periodically the tooling will receive a deployment exception (configuration already exists)
when publishing updates. The user must remove the projects, manually delete from the repository,
and then re-add/re-publish. Occasionally, you must restart both the tooling and the runtime
in order to delete from repository.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message