[
https://issues.apache.org/jira/browse/SLING-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3441.
-------------------------------------
Resolution: Fixed
I've changed the implementation to use a per request resource resolver if
possible. Otherwise the shared resolver is still used, but it's refreshed before
> 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)
