[ http://issues.apache.org/jira/browse/GERONIMO-770?page=comments#action_12359871 ]
Calvin Austin commented on GERONIMO-770: ---------------------------------------- There is an artificial way to reproduce this I discovered by accident. Simply start org/apache/geronimo/DeployerSystem To then get your geronimo back into a useable state you can edit var/config/config.list and remove DeployerSystem and restart the server > java.lang.IllegalStateException: More then one configuration mananger was > found in kernel > ----------------------------------------------------------------------------------------- > > Key: GERONIMO-770 > URL: http://issues.apache.org/jira/browse/GERONIMO-770 > Project: Geronimo > Type: Bug > Components: deployment > Reporter: Jeremy Boynes > Assignee: Aaron Mulder > Fix For: 1.0 > > 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. - 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
