[
https://issues.apache.org/jira/browse/SLING-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-3160:
---------------------------------------
Assignee: Carsten Ziegeler
> Creating ResourceResolverFactory as ServiceFactory leads to multiple
> MapEntries creation
> ----------------------------------------------------------------------------------------
>
> Key: SLING-3160
> URL: https://issues.apache.org/jira/browse/SLING-3160
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Affects Versions: Resource Resolver 1.1.0
> Reporter: Chetan Mehrotra
> Assignee: Carsten Ziegeler
> Attachments: threaddump.txt
>
>
> With SLING-2944 ResourceResolverFactory is now being created as
> ServiceFactory leading to multiple instances being created for each consuming
> bundle.
> Each ResourceResolverFactoryImpl instance keeps a reference to MapEntries
> which internally spawns a thread to keep the entries upto date. Due to
> creation of multiple instances there are multiple "MapEntries Update" thread
> getting created which is probably not desirable.
> I think all the ResourceResolverFactoryImpl must *share* a singleton state
> where only single instance of MapEntries gets created
--
This message was sent by Atlassian JIRA
(v6.1#6144)
