[
https://issues.apache.org/jira/browse/ARIES-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved ARIES-1627.
------------------------------------
Resolution: Fixed
Fix Version/s: jmx-core-1.1.8
Committing to https://svn.apache.org/repos/asf/aries/trunk ...
M
jmx/jmx-core/src/main/java/org/apache/aries/jmx/framework/BundleState.java
M
jmx/jmx-core/src/main/java/org/apache/aries/jmx/framework/ServiceState.java
M
jmx/jmx-core/src/main/java/org/apache/aries/jmx/framework/StateConfig.java
M
jmx/jmx-core/src/test/java/org/apache/aries/jmx/framework/BundleStateTest.java
M
jmx/jmx-core/src/test/java/org/apache/aries/jmx/framework/ServiceStateTest.java
Committed r1764533
Also added a flag for bundles for coherence.
> Give ability to disable JMX notifications generation in case of OSGi service
> changes
> ------------------------------------------------------------------------------------
>
> Key: ARIES-1627
> URL: https://issues.apache.org/jira/browse/ARIES-1627
> Project: Aries
> Issue Type: Improvement
> Components: JMX
> Affects Versions: jmx-1.1.5
> Reporter: Dmitry Konstantinov
> Assignee: Guillaume Nodet
> Labels: performance
> Fix For: jmx-core-1.1.8
>
> Attachments: ARIES-1627.patch
>
>
> Aries JMX generates JMX notifications for all OSGi service changes events:
> * During a startup a lot of OSGi services are published.
> * Generation of JMX notifications takes some time (it can take about 0.7-1
> seconds total on some live Karaf instances), getServiceIds retrieves each
> time all service references and so on.
> * these JMX notifications frequently are not needed
> It would be useful to have a configuration option to disable JMX
> notifications for OSGi service changes (it can be an Config Admin option in
> org.apache.aries.jmx.framework.StateConfig)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
