felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-3039) SCR cleans up delayed service components too aggressively
Date Mon, 17 Oct 2011 10:08:11 GMT

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

Felix Meschberger resolved FELIX-3039.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: scr-1.6.2
         Assignee: Felix Meschberger

In Rev. 1185082: Added new ds.delayed.keepInstances configuration property which allows to
prevent delayed components from being clean up. By default this property is false (to implement
the spec suggestion). The property can be set as a framework property or as part of the org.apache.felix.scr.ScrService
configuration.

Also updated documentation at http://felix.apache.org/site/apache-felix-service-component-runtime.html#ApacheFelixServiceComponentRuntime-Configuration
                
> SCR cleans up delayed service components too aggressively
> ---------------------------------------------------------
>
>                 Key: FELIX-3039
>                 URL: https://issues.apache.org/jira/browse/FELIX-3039
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>            Reporter: Neil Bartlett
>            Assignee: Felix Meschberger
>            Priority: Minor
>             Fix For: scr-1.6.2
>
>
> In the case of an ordinary delayed service component, SCR immediately deactivates and
destroys the component when its service is released by the consumer. In cases where a consumer
occasionally binds and invokes the service (e.g. EventAdmin) this can cause the component
to be continuously destroyed and recreated.
> Note that Equinox's DS offers a little more control, we can choose either to immediately
clean up or never clean up (and the default is never). This is still not very satisfactory
though.
> I think ideally there should be a configurable timeout, so that a component will be cleaned
up only if it is not used for some time. I also think the default should be quite long, e.g.
many minutes.

--
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