You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jeremy Boynes (JIRA)" <de...@geronimo.apache.org> on 2005/07/17 20:22:10 UTC
[jira] Created: (GERONIMO-770) java.lang.IllegalStateException: More then one configuration mananger was found in kernel
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
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
[jira] Closed: (GERONIMO-770) java.lang.IllegalStateException: More
then one configuration mananger was found in kernel
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (GERONIMO-770) java.lang.IllegalStateException: More then one configuration mananger was found in kernel
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-770?page=all ]
Aaron Mulder updated GERONIMO-770:
----------------------------------
Fix Version: 1.0-M5
Assign To: Aaron Mulder
Do you have an app client I could use to reproduce this?
> 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-M5
>
> 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
[jira] Updated: (GERONIMO-770) java.lang.IllegalStateException: More then one configuration mananger was found in kernel
Posted by "David Blevins (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-770?page=all ]
David Blevins updated GERONIMO-770:
-----------------------------------
Fix Version: 1.0
(was: 1.0-M5)
> 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
[jira] Updated: (GERONIMO-770) java.lang.IllegalStateException:
More then one configuration mananger was found in kernel
Posted by "Matt Hogstrom (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-770?page=all ]
Matt Hogstrom updated GERONIMO-770:
-----------------------------------
Fix Version/s: Wish List
(was: 1.2)
> 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
> Issue Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
> 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.
-
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-770) java.lang.IllegalStateException:
More then one configuration mananger was found in kernel
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-770?page=all ]
Dain Sundstrom updated GERONIMO-770:
------------------------------------
Assign To: (was: Dain Sundstrom)
> 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
> Fix For: 1.2
>
> 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
[jira] Assigned: (GERONIMO-770) java.lang.IllegalStateException:
More then one configuration mananger was found in kernel
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-770?page=all ]
Dain Sundstrom reassigned GERONIMO-770:
---------------------------------------
Assign To: Dain Sundstrom (was: Aaron Mulder)
> 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: Dain Sundstrom
> Fix For: 1.2
>
> 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
[jira] Commented: (GERONIMO-770) java.lang.IllegalStateException: More then one configuration mananger was found in kernel
Posted by "Calvin Austin (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Updated: (GERONIMO-770) java.lang.IllegalStateException: More then one configuration mananger was found in kernel
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-770?page=all ]
Dain Sundstrom updated GERONIMO-770:
------------------------------------
Fix Version: 1.1
(was: 1.0)
> 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.1
>
> 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