Hi Roy
Do your Site objects reference a resource resolver instance, e.g. via
a resource? If they do then it's likely the warning comes from this RR
being used concurrently.
Other than that (bar closing the RRs in the thread), I can't see
anything obviously wrong with your last code snippet.
Rega
Hey guys,
Thanks for the replies.
In the getServiceResourceResolver I do actually call
resourceResolverFactory.getServiceResourceResolver, making it a new resource
resolver instance for every thread. so in my knowledge this does create a new
session, but it's on the same user name?
Greets,
Ro
Hi,
Sorry for missing the original post on the Oak list.
Like Carsten said, sessions do not support multiple threads. See also
https://docs.adobe.com/docs/en/spec/jcr/2.0/4_Connecting.html
The warning you receive is from a protection mechanism in Oak that
prevents the worst. I.e. data corr
Hi,
a resource resolver is single threaded and must not be used concurrently
by multiple threads. Main driver (but not the only one) is the JCR
session which requires this.
However, there is nothing in the Sling code base blocking you from doing
so anyways. So we don't have any additional ch
Hey sling users,
This is a repost from the userlist of oak because I didn't get a reply there,
so I hope I might get one here:
We have a system that migrates our sites based on migration rules, the
psuedocode is as the following:
resourceResolver = getServiceResourceResolver("migration-user")
