[
https://issues.apache.org/jira/browse/ARIES-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned ARIES-756:
------------------------------------------
Assignee: Jean-Baptiste Onofré
> Excessive warning if JMXAgentImpl starts before MBeanServer service
> -------------------------------------------------------------------
>
> Key: ARIES-756
> URL: https://issues.apache.org/jira/browse/ARIES-756
> Project: Aries
> Issue Type: Bug
> Components: JMX
> Affects Versions: 0.3
> Environment: Karaf 2.2.2, Talend Service Factory 2.4.2.0
> Reporter: Chris Dolan
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
>
> In my Karaf container, the MBeanServer is registered with the OSGi framework
> via org.apache.karaf.management. The default configuration has that bundle
> and org.apache.aries.jmx starting at the same startlevel. Sometimes the Aries
> JMXAgentImpl boots first and sometimes the MBeanServer boots first. When
> JMXAgentImpl boots first, I get ominous messages like the following:
> 2011-10-05 15:31:12,995 WARN [Logger.java:52] There are no MBean servers
> registred, can't register MBeans - org.apache.aries.jmx
> Really, this message is harmless because a moment later the MBeanServer is
> registered and the JMXAgentImpl.registerMBeans() method registers all of the
> beans. So I recommend that this warning be downgraded to a debug message or
> just deleted. Perhaps the message should be changed to:
> There are no MBean servers registered yet, will register all beans when a
> server is discovered.
> (note that "registered" is misspelled as "registred" in the code right now)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
