[jboss-osgi-issues] [JBoss JIRA] Updated: (JBOSGI-453) JMX related exception when starting OSGi subsystem

Thomas Diesler (JIRA) jira-events at lists.jboss.org
Thu Jun 23 05:36:23 EDT 2011


     [ https://issues.jboss.org/browse/JBOSGI-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler updated JBOSGI-453:
----------------------------------

    Fix Version/s: JBossOSGi 1.0.1
                       (was:  JBossOSGi 1.0.0)


Revisit for next release

> JMX related exception when starting OSGi subsystem
> --------------------------------------------------
>
>                 Key: JBOSGI-453
>                 URL: https://issues.jboss.org/browse/JBOSGI-453
>             Project: JBoss OSGi
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jboss-osgi-jmx
>            Reporter: David Bosschaert
>            Assignee: Thomas Diesler
>             Fix For: JBossOSGi 1.0.1
>
>
> Very often when the OSGi subsystem comes up, I'm seeing the following exception:
> 08:32:43,709 INFO  [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-1) Bundle started: org.apache.aries.jmx:0.1.0.incubating
> 08:32:43,710 INFO  [org.apache.aries.jmx] (Thread-14) Registering org.osgi.jmx.service.cm.ConfigurationAdminMBean to MBeanServer org.jboss.as.jmx.tcl.TcclMBeanServer at 7d093a with name osgi.compendium:service=cm,version=1.3
> 08:32:43,711 INFO  [org.apache.aries.jmx] (Thread-14) Registering org.osgi.jmx.framework.BundleStateMBean to MBeanServer org.jboss.as.jmx.tcl.TcclMBeanServer at 7d093a with name osgi.core:type=bundleState,version=1.5
> 08:32:43,724 INFO  [org.apache.aries.jmx] (Thread-14) Registering org.osgi.jmx.framework.ServiceStateMBean to MBeanServer org.jboss.as.jmx.tcl.TcclMBeanServer at 7d093a with name osgi.core:type=serviceState,version=1.5
> 08:32:43,725 INFO  [org.apache.aries.jmx] (Thread-14) Registering org.osgi.jmx.service.cm.ConfigurationAdminMBean to MBeanServer org.jboss.as.jmx.tcl.TcclMBeanServer at 7d093a with name osgi.compendium:service=cm,version=1.3
> 08:32:43,726 ERROR [org.apache.aries.jmx] (Thread-14) 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) [:1.6.0_23]
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484) [:1.6.0_23]
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963) [:1.6.0_23]
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917) [:1.6.0_23]
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312) [:1.6.0_23]
> 	at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) [:1.6.0_23]
> 	at org.jboss.as.jmx.tcl.TcclMBeanServer.registerMBean(TcclMBeanServer.java:238)
> 	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) [:1.6.0_23]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_23]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_23]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23]
> 	at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-osgi-issues mailing list