You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Felix Meschberger (Created) (JIRA)" <ji...@apache.org> on 2011/11/15 13:37:51 UTC
[jira] [Created] (ARIES-782) AbstractCompendiumHandler uses
ServiceTracker.getTrackingCount in the wrong way
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
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
[jira] [Updated] (ARIES-782) AbstractCompendiumHandler uses
ServiceTracker.getTrackingCount in the wrong way
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (ARIES-782) AbstractCompendiumHandler uses
ServiceTracker.getTrackingCount in the wrong way
Posted by "Felix Meschberger (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated ARIES-782:
------------------------------------
Attachment: ARIES-782.patch
Proposed patch: Use trackedId field instead of ServiceTracker.trackingCount assuming that trackedId always only contains a non-null value if a service is registered with JMX
> 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
> 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
[jira] [Assigned] (ARIES-782) AbstractCompendiumHandler uses
ServiceTracker.getTrackingCount in the wrong way
Posted by "Felix Meschberger (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reassigned ARIES-782:
---------------------------------------
Assignee: Felix Meschberger
> 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
> 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
[jira] [Resolved] (ARIES-782) AbstractCompendiumHandler uses
ServiceTracker.getTrackingCount in the wrong way
Posted by "Felix Meschberger (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved ARIES-782.
-------------------------------------
Resolution: Fixed
Fix Version/s: 0.4
Applied the patch in Rev. 1227542
> 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
>
> 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