aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-897) The ReferenceRecipe lazily get the real osgi service which cause service tracking count to be inaccurate
Date Wed, 01 Aug 2012 16:20:03 GMT

    [ https://issues.apache.org/jira/browse/ARIES-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426730#comment-13426730
] 

Guillaume Nodet commented on ARIES-897:
---------------------------------------

Actually, the problem is different. The bad usage comes from the fact that the ReferenceRecipe#bind()
is called twice.
Once when the manager is started, and once when the recipe is created to make sure listeners
are called.
This second call cause the ungetService() method to be called and lower the usage of the service.
The service should only be unget if the new tracked ServiceReference is different from the
old one.
                
> The ReferenceRecipe lazily get the real osgi service which cause service tracking count
to be inaccurate
> --------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-897
>                 URL: https://issues.apache.org/jira/browse/ARIES-897
>             Project: Aries
>          Issue Type: Bug
>            Reporter: Guillaume Nodet
>
> Service tracking count is used to order the bundles when stopping those.
> If the order is wrong, it can cause some bundles to go into the default 5 minutes timeout
when trying to access 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

        

Mime
View raw message