You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2014/03/31 13:11:15 UTC

[jira] [Closed] (SLING-3441) Avoid shared resource resolver usage

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

Carsten Ziegeler closed SLING-3441.
-----------------------------------


> Avoid shared resource resolver usage
> ------------------------------------
>
>                 Key: SLING-3441
>                 URL: https://issues.apache.org/jira/browse/SLING-3441
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>    Affects Versions: Servlets Resolver 2.3.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Servlets Resolver 2.3.2
>
>
> The servlet resolver uses a single shared rsource resolver to resolve scripts. Resource resolvers are not thread safe and therefore should not be used at the same time from different threads.
> Apart from that, this creates a bottleneck as the repository implementations (Jackrabbit, Oak) synchronize all access in this case - which then ultimately synchronises all requests. This is even more problematic as the servlet resolver is hit alot during a single request



--
This message was sent by Atlassian JIRA
(v6.2#6252)