[
https://issues.apache.org/jira/browse/SLING-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941403#comment-13941403
]
Carsten Ziegeler commented on SLING-3441:
-----------------------------------------
This change causes some script engines to fail like the javascript script
engine which reads the script resource on each access. The first access works,
subsequent requests fail as the resource resolver has been closed.
> 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)
