You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2012/05/22 16:13:42 UTC

[jira] [Updated] (ARIES-782) AbstractCompendiumHandler uses ServiceTracker.getTrackingCount in the wrong way

     [ https://issues.apache.org/jira/browse/ARIES-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated ARIES-782:
----------------------------------

    Fix Version/s: blueprint-core-0.3.2
    
> AbstractCompendiumHandler uses ServiceTracker.getTrackingCount in the wrong way
> -------------------------------------------------------------------------------
>
>                 Key: ARIES-782
>                 URL: https://issues.apache.org/jira/browse/ARIES-782
>             Project: Aries
>          Issue Type: Bug
>          Components: JMX
>    Affects Versions: 0.3
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 0.4, blueprint-core-0.3.2
>
>         Attachments: ARIES-782.patch
>
>
> The AbstractCompendiumHandler.addingService calls the ServiceTracker.getTrackingCount() to obviously check the number of services registered under the same name. Of course, for Compendium services, the framework is assumed to only have one (though, I am not sure, whether JMX should really be picky here...)
> The problem is that getTrackingCount really is a counter for the service changes and is incremented on each service event. As such this counter cannot be used to get the number of tracked services.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira