[
https://issues.apache.org/jira/browse/FELIX-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064793#comment-13064793
]
Neil Bartlett commented on FELIX-3039:
--------------------------------------
Not in a generic way because the spec does not state any such parameter name.
Equinox uses a system property "equinox.scr.dontDisposeInstances"
(http://wiki.eclipse.org/Equinox/RuntimeOptions) which can be true or false
(default is true).
> 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
> Priority: Minor
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
