You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/12/12 19:26:00 UTC
[jira] [Updated] (SLING-10994) Remove locking of JCR node
[ https://issues.apache.org/jira/browse/SLING-10994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-10994:
------------------------------------
Description:
Currently starting the jcr.contentloader bundle and loading initial content bundles leads to the following warning (e.g. in Sling Starter 12-SNAPSHOT)
{code}
org.apache.jackrabbit.oak.jcr.lock.LockDeprecation Support for JCR Locking is deprecated and will be disabled in a future version of Jackrabbit Oak (see OAK-6421 for further information) - operation 'addMixin mix:lockable' called from: org.apache.sling.jcr.contentloader.internal.BundleContentLoaderListener.getBundleContentInfo(BundleContentLoaderListener.java:343) org.apache.sling.jcr.contentloader.internal.BundleContentLoader.registerBundleInternal(BundleContentLoader.java:155) org.apache.sling.jcr.contentloader.internal.BundleContentLoader.registerBundle(BundleContentLoader.java:122) org.apache.sling.jcr.contentloader.internal.BundleContentLoaderListener.loadBundle(BundleContentLoaderListener.java:266) org.apache.sling.jcr.contentloader.internal.BundleContentLoaderListener.activate(BundleContentLoaderListener.java:246)
{code}
Locking is currently used to make sure that in a clustered environment (i.e. multiple sling instances leveraging the same repository) initial-content is only processed once.
Depending on the bundle location one might process content initialisation only on the [cluster leader|https://sling.apache.org/documentation/bundles/discovery-api-and-impl.html#instance-instancedescription].
For bundles which are only installed one one cluster instance (e.g. local installation) initial-content should always be performed (after checking the potentially existing bundle content info from the repo).
was:
Currently starting the jcr.contentloader bundle and loading initial content bundles leads to the following warning (e.g. in Sling Starter 12-SNAPSHOT)
{code}
org.apache.jackrabbit.oak.jcr.lock.LockDeprecation Support for JCR Locking is deprecated and will be disabled in a future version of Jackrabbit Oak (see OAK-6421 for further information) - operation 'addMixin mix:lockable' called from: org.apache.sling.jcr.contentloader.internal.BundleContentLoaderListener.getBundleContentInfo(BundleContentLoaderListener.java:343) org.apache.sling.jcr.contentloader.internal.BundleContentLoader.registerBundleInternal(BundleContentLoader.java:155) org.apache.sling.jcr.contentloader.internal.BundleContentLoader.registerBundle(BundleContentLoader.java:122) org.apache.sling.jcr.contentloader.internal.BundleContentLoaderListener.loadBundle(BundleContentLoaderListener.java:266) org.apache.sling.jcr.contentloader.internal.BundleContentLoaderListener.activate(BundleContentLoaderListener.java:246)
{code}
> Remove locking of JCR node
> --------------------------
>
> Key: SLING-10994
> URL: https://issues.apache.org/jira/browse/SLING-10994
> Project: Sling
> Issue Type: Improvement
> Affects Versions: JCR ContentLoader 2.4.2
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: JCR ContentLoader 2.5.0
>
>
> Currently starting the jcr.contentloader bundle and loading initial content bundles leads to the following warning (e.g. in Sling Starter 12-SNAPSHOT)
> {code}
> org.apache.jackrabbit.oak.jcr.lock.LockDeprecation Support for JCR Locking is deprecated and will be disabled in a future version of Jackrabbit Oak (see OAK-6421 for further information) - operation 'addMixin mix:lockable' called from: org.apache.sling.jcr.contentloader.internal.BundleContentLoaderListener.getBundleContentInfo(BundleContentLoaderListener.java:343) org.apache.sling.jcr.contentloader.internal.BundleContentLoader.registerBundleInternal(BundleContentLoader.java:155) org.apache.sling.jcr.contentloader.internal.BundleContentLoader.registerBundle(BundleContentLoader.java:122) org.apache.sling.jcr.contentloader.internal.BundleContentLoaderListener.loadBundle(BundleContentLoaderListener.java:266) org.apache.sling.jcr.contentloader.internal.BundleContentLoaderListener.activate(BundleContentLoaderListener.java:246)
> {code}
> Locking is currently used to make sure that in a clustered environment (i.e. multiple sling instances leveraging the same repository) initial-content is only processed once.
> Depending on the bundle location one might process content initialisation only on the [cluster leader|https://sling.apache.org/documentation/bundles/discovery-api-and-impl.html#instance-instancedescription].
> For bundles which are only installed one one cluster instance (e.g. local installation) initial-content should always be performed (after checking the potentially existing bundle content info from the repo).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)