[jboss-osgi-issues] [JBoss JIRA] Work started: (JBOSGI-298) InstanceAlreadyExistsException: osgi.core:type=framework, version=1.5

InstanceAlreadyExistsException: osgi.core:type=framework,version=1.5 -------------------------------------------------------------------- Key: JBOSGI-298 URL: https://jira.jboss.org/jira/browse/JBOSGI-298 Project: JBoss OSGi Issue Type: Bug Security Level: Public(Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta7 MBeans might get registered twice. 2010-03-04 20:40:11,113 INFO [org.apache.aries.jmx] Registering org.osgi.jmx.framework.ServiceStateMBean to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@ce16ad with name osgi.core:type=serviceState,version=1.5 2010-03-04 20:40:11,131 INFO [org.apache.aries.jmx] Registering org.osgi.jmx.framework.BundleStateMBean to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@ce16ad with name osgi.core:type=bundleState,version=1.5 2010-03-04 20:40:11,134 INFO [org.apache.aries.jmx] Registering org.osgi.jmx.framework.PackageStateMBean to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@ce16ad with name osgi.core:type=packageState,version=1.5 2010-03-04 20:40:11,136 ERROR [org.apache.aries.jmx] MBean is already registered org.apache.felix.log.LogException: javax.management.InstanceAlreadyExistsException: osgi.core:type=packageState,version=1.5 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:128) 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) This is probably due to a asynchronous delay of a previous unregister