You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2007/07/31 02:35:52 UTC

[jira] Closed: (GERONIMO-770) java.lang.IllegalStateException: More then one configuration mananger was found in kernel

     [ https://issues.apache.org/jira/browse/GERONIMO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed GERONIMO-770.
---------------------------------

    Resolution: Fixed
      Assignee: David Jencks

It's possible to make things like this happen if you manage to start an app client in the server, but it doesn't seem to happen unless you explicitly try to do that: certainly not as a result of a failed deployment.

> java.lang.IllegalStateException: More then one configuration mananger was found in kernel
> -----------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-770
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-770
>             Project: Geronimo
>          Issue Type: Bug
>          Components: deployment
>            Reporter: Jeremy Boynes
>            Assignee: David Jencks
>             Fix For: Wish List
>
>
> Seems to occur after unsuccessful deployment of an application client. Could be that the org/apache/geronimo/Client configuration is left running so that two GBeans are present.
> Once this occurs, the deployment tools are unable to locate the correct configuration manager causing all deployment attempts to fail.

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