[jira] [Created] (ARIES-1119) MBean registration race condition in JMXAgentImpl
Tuomas Kiviaho created ARIES-1119:
-
Summary: MBean registration race condition in JMXAgentImpl
Key: ARIES-1119
URL: https://issues.apache.org/jira/browse/ARIES-1119
Project: Aries
Issue Type: Bug
Components: JMX
Affects Versions: jmx-core-1.0.2
Environment: jmx-core-1.1.1
Reporter: Tuomas Kiviaho
Priority: Minor
I'm just starting to use Aries JMX Whiteboard but the first thing to struck me
was an innocent but yet disturbing error message.
{code}
[INFO] [org.visit] Registering org.osgi.jmx.service.cm.ConfigurationAdminMBean
to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@82a72a with name
osgi.compendium:service=cm,version=1.3,framework=org.apache.felix.framework,uuid=c16979bc-e552-4a51-8763-a41d385589c8
[INFO] [org.visit] Registering org.osgi.jmx.framework.FrameworkMBean to
MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@82a72a with name
osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=c16979bc-e552-4a51-8763-a41d385589c8
[INFO] [org.visit] Registering org.osgi.jmx.service.cm.ConfigurationAdminMBean
to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@82a72a with name
osgi.compendium:service=cm,version=1.3,framework=org.apache.felix.framework,uuid=c16979bc-e552-4a51-8763-a41d385589c8
[WARNING] [org.visit] MBean is already registered
org.apache.felix.log.LogException:
javax.management.InstanceAlreadyExistsException:
osgi.compendium:service=cm,version=1.3,framework=org.apache.felix.framework,uuid=c16979bc-e552-4a51-8763-a41d385589c8
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
at org.apache.aries.jmx.agent.JMXAgentImpl.registerMBean(.:194)
at org.apache.aries.jmx.agent.JMXAgentContext.registerMBean(.:74)
at org.apache.aries.jmx.AbstractCompendiumHandler$1.run(.:91)
{code}
It seems that JMXAgentImpl is not keeping track on which server it has
registered which mbean instance so it tries to register already registered
beans again. With a small effort, the current mbeans handlers tracking table
could be changed to contain mbean servers instead of a simple flag indicating
whether mbean has been registered or not.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
Re: [VOTE] Blueprint parser 1.1.0 and blueprint-core 1.2.0
+1 assuming the RAT failure I received [1] can be safely ignored. John [1] RAT FAILURE:? src/main/resources/org/apache/aries/blueprint/ext/impl/xml.xsd [VOTE] Blueprint parser 1.1.0 and blueprint-core 1.2.0 The Karaf community needs new releases of blueprint parser/core so they can do their new 3.0 release.It's been about 9 months since the last releases anyway so we should try and get some fixes out there. Tags: http://svn.apache.org/repos/asf/aries/tags/blueprint-parser-1.1.0/ http://svn.apache.org/repos/asf/aries/tags/ org.apache.aries.blueprint.core-1.2.0/ Staging area: https://repository.apache.org/content/repositories/orgapachearies-121/ Here is my +1. Vote will remain open for at least 72h. -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com [attachment signature.asc deleted by John W Ross/Atlanta/IBM]
[jira] [Created] (ARIES-1120) getComponentIds returns the context/bundle/etc... even during a reset
Daniel Kulp created ARIES-1120: -- Summary: getComponentIds returns the context/bundle/etc... even during a reset Key: ARIES-1120 URL: https://issues.apache.org/jira/browse/ARIES-1120 Project: Aries Issue Type: Bug Components: Blueprint Reporter: Daniel Kulp Assignee: Daniel Kulp A bundle refresh will cause the componentDefinitionRegistry to be reset() (which is OK). However, if a call is made to getComponentIds() between the reset call and the call to populate the registry, the returned Set contains entries for blueprintContainer, blueprintBundle, blueprintBundleContext, and blueprintConverter. If you then try to lookup the metadata for those, an exception is thrown. Likely the call to getComponentIds() should not automatically add those. In addition, immediately after reset, we should re-add those to make sure they are available. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (ARIES-1120) getComponentIds returns the context/bundle/etc... even during a reset
[ https://issues.apache.org/jira/browse/ARIES-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved ARIES-1120. Resolution: Fixed Fix Version/s: blueprint-core-1.2.1 getComponentIds returns the context/bundle/etc... even during a reset - Key: ARIES-1120 URL: https://issues.apache.org/jira/browse/ARIES-1120 Project: Aries Issue Type: Bug Components: Blueprint Reporter: Daniel Kulp Assignee: Daniel Kulp Fix For: blueprint-core-1.2.1 A bundle refresh will cause the componentDefinitionRegistry to be reset() (which is OK). However, if a call is made to getComponentIds() between the reset call and the call to populate the registry, the returned Set contains entries for blueprintContainer, blueprintBundle, blueprintBundleContext, and blueprintConverter. If you then try to lookup the metadata for those, an exception is thrown. Likely the call to getComponentIds() should not automatically add those. In addition, immediately after reset, we should re-add those to make sure they are available. -- This message was sent by Atlassian JIRA (v6.1#6144)
Jenkins build is unstable: AriesWithSnapshotDependencies #428
See https://builds.apache.org/job/AriesWithSnapshotDependencies/428/changes
