[
https://issues.apache.org/jira/browse/ARIES-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236582#comment-13236582
]
Guillaume Nodet commented on ARIES-663:
---------------------------------------
I have the same issue from times to time. Not sure what really happen but I've
seen in the log that the CM mean was being registered twice which obviously
lead to this exception. Though I only have a single copy of the felix
configadmin bundle deployed ....
> ConfigurationAdminMBean registered twice
> ----------------------------------------
>
> Key: ARIES-663
> URL: https://issues.apache.org/jira/browse/ARIES-663
> Project: Aries
> Issue Type: Bug
> Affects Versions: 0.3
> Reporter: Thomas Diesler
>
> {code}
> 18:00:12,965 INFO [jmx] Starting JMX OSGi agent
> 18:00:12,982 INFO [jmx] Registering MBean with ObjectName
> [osgi.compendium:service=cm,version=1.3] for service with service.id [12]
> 18:00:12,990 INFO [HostBundleState] Bundle started:
> org.apache.aries.jmx:0.3.0
> 18:00:12,993 INFO [HostBundleState] Bundle started:
> org.apache.aries.util:0.3.0
> 18:00:12,994 INFO [jmx] Registering
> org.osgi.jmx.service.cm.ConfigurationAdminMBean to MBeanServer
> com.sun.jmx.mbeanserver.JmxMBeanServer@5d5bdc50 with name
> osgi.compendium:service=cm,version=1.3
> 18:00:13,003 INFO [jmx] Registering org.osgi.jmx.framework.BundleStateMBean
> to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@5d5bdc50 with name
> osgi.core:type=bundleState,version=1.5
> 18:00:13,005 INFO [jmx] Registering org.osgi.jmx.framework.PackageStateMBean
> to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@5d5bdc50 with name
> osgi.core:type=packageState,version=1.5
> 18:00:13,006 INFO [jmx] Registering org.osgi.jmx.framework.ServiceStateMBean
> to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@5d5bdc50 with name
> osgi.core:type=serviceState,version=1.5
> 18:00:13,007 INFO [jmx] Registering
> org.osgi.jmx.service.cm.ConfigurationAdminMBean to MBeanServer
> com.sun.jmx.mbeanserver.JmxMBeanServer@5d5bdc50 with name
> osgi.compendium:service=cm,version=1.3
> 18:00:13,009 ERROR [jmx] MBean is already registered
> org.apache.felix.log.LogException:
> javax.management.InstanceAlreadyExistsException:
> osgi.compendium:service=cm,version=1.3
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
> at
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
> at
> org.apache.aries.jmx.agent.JMXAgentImpl.registerMBeans(JMXAgentImpl.java:129)
> at
> org.apache.aries.jmx.agent.JMXAgentContext.registerMBeans(JMXAgentContext.java:58)
> at
> org.apache.aries.jmx.MBeanServiceTracker$1.run(MBeanServiceTracker.java:61)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> 18:00:13,010 INFO [jmx] Registering org.osgi.jmx.framework.FrameworkMBean to
> MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@5d5bdc50 with name
> osgi.core:type=framework,version=1.5
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
