[jira] [Closed] (SLING-3400) Sling holds resource providers after they have been unregistered

[ https://issues.apache.org/jira/browse/SLING-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-3400. --- > Sling holds resource providers after they have been unregiste

[jira] [Resolved] (SLING-3400) Sling holds resource providers after they have been unregistered

[ https://issues.apache.org/jira/browse/SLING-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3400. - Resolution: Fixed > Sling holds resource providers after they have been unregistered > --

[jira] [Commented] (SLING-3400) Sling holds resource providers after they have been unregistered

[ https://issues.apache.org/jira/browse/SLING-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908289#comment-13908289 ] Carsten Ziegeler commented on SLING-3400: - In rev 1570565 I've committed a change

Re: (SLING-3400) Sling holds resource providers after they have been unregistered

I've committed a patch which will now unregister the resource resolver factory if a resource provider factory is unregistered. This is actually very simple as we already have all the code in the right place (ResourceresolverFactoryActivator). I tested this a little bit and it seems too not cause pr

Re: (SLING-3400) Sling holds resource providers after they have been unregistered

I just gave this a try run with a large application...and it seems that this is causing too much service registration changes as there are many components having a reference to the resource resolver...or in other words the app never finishes its startup I guess the main problem is that now, the re

Re: (SLING-3400) Sling holds resource providers after they have been unregistered

Yes, that sounds like the easiest option - it would mean that the resource resolver factory is re-registered with every change to a resource provider factory - which doesn't sound too bad to me Carsten 2014-02-20 13:25 GMT+01:00 Felix Meschberger : > Hi > > I see. > > Can this be easily "solved

Re: (SLING-3400) Sling holds resource providers after they have been unregistered

Hi I see. Can this be easily "solved" by just making the ResourceProviderFactory reference in the ResourceResolverFactoryActivator a static reference with eager policyOption? Regards Felix Am 20.02.2014 um 13:21 schrieb Carsten Ziegeler : > Only ResourceProviderFactories are affected - simpl

Re: (SLING-3400) Sling holds resource providers after they have been unregistered

Only ResourceProviderFactories are affected - simple resourceProviders like the servlet ones can't keep state. Those appear/disappear silently. I agree that service registration modifications are rather expensive, on the other hand there are only a few provider factories and those are usually not u

Re: (SLING-3400) Sling holds resource providers after they have been unregistered

Hi Am 20.02.2014 um 10:19 schrieb Carsten Ziegeler : > Hi, > > as noted in SLING-3400 we have a problem when a resource provider factory > is unregistered and a resource resolver is currently using a provider from > this factory. In that case, that reference is never cleared. > This problem occ

(SLING-3400) Sling holds resource providers after they have been unregistered

Hi, as noted in SLING-3400 we have a problem when a resource provider factory is unregistered and a resource resolver is currently using a provider from this factory. In that case, that reference is never cleared. This problem occurs due to long running resource resolvers. I looked at solving th

[jira] [Commented] (SLING-3400) Sling holds resource providers after they have been unregistered

[ https://issues.apache.org/jira/browse/SLING-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906786#comment-13906786 ] Carsten Ziegeler commented on SLING-3400: - It seems this is really caused by long

[jira] [Commented] (SLING-3400) Sling holds resource providers after they have been unregistered

[ https://issues.apache.org/jira/browse/SLING-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905084#comment-13905084 ] Carsten Ziegeler commented on SLING-3400: - [~lbyrum] Can you confirm / verify that

[jira] [Assigned] (SLING-3400) Sling holds resource providers after they have been unregistered

[ https://issues.apache.org/jira/browse/SLING-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-3400: --- Assignee: Carsten Ziegeler > Sling holds resource providers after they have been unre

[jira] [Updated] (SLING-3400) Sling holds resource providers after they have been unregistered

[ https://issues.apache.org/jira/browse/SLING-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3400: Fix Version/s: Resource Resolver 1.1.0 > Sling holds resource providers after they have bee

[jira] [Created] (SLING-3400) Sling holds resource providers after they have been unregistered

Laurie byrum created SLING-3400: --- Summary: Sling holds resource providers after they have been unregistered Key: SLING-3400 URL: https://issues.apache.org/jira/browse/SLING-3400 Project: Sling