You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Dmitry Konstantinov (JIRA)" <ji...@apache.org> on 2016/10/12 17:51:20 UTC
[jira] [Updated] (ARIES-1627) Give ability to disable JMX
notifications generation in case of OSGi service changes
[ https://issues.apache.org/jira/browse/ARIES-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitry Konstantinov updated ARIES-1627:
---------------------------------------
Description:
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 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)
was:
Aries JMX generates JMX notifications for all OSGi service changes events. 1) During a startup a lot of OSGi services are published.
2) Generation of JMX notifications takes some time (it can take about 0.7-1 seconds on some live Karaf instances), getServiceIds retrieves each time all service references and so on.
3) 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)
> 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
>
> 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 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)