You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Joerg Hoh (Jira)" <ji...@apache.org> on 2026/08/13 18:06:00 UTC

[jira] [Resolved] (OAK-12356) Improve log warning

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

Joerg Hoh resolved OAK-12356.
-----------------------------
    Fix Version/s: 2.6.0
       Resolution: Fixed

> Improve log warning
> -------------------
>
>                 Key: OAK-12356
>                 URL: https://issues.apache.org/jira/browse/OAK-12356
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: security
>    Affects Versions: 1.88.0, 2.0.0
>            Reporter: Joerg Hoh
>            Assignee: Joerg Hoh
>            Priority: Major
>             Fix For: 2.6.0
>
>
>  
> Assuming this content structure:
> {noformat}
> Node foo (jcr:primaryType=nt:unstructured)
>   + Node rep:policy (jcr:primaryType=nt:unstructed)
> {noformat}
> then trying to add ACLs on {{foo}} will fail with a message like this:
> {noformat}
> 13.08.2026 10:00:17.450 *WARN* [Apache Sling Repository Startup Thread #1] org.apache.jackrabbit.oak.security.authorization.accesscontrol.AccessControlManagerImpl Colliding policy child without node being access controllable (/foo).
> 13.08.2026 10:00:17.452 *ERROR* [Apache Sling Repository Startup Thread #1] com.adobe.granite.repository.impl.SlingRepositoryManager Exception in a SlingRepositoryInitializer, SlingRepository service registration aborted
> javax.jcr.RepositoryException: Applying repoinit operation failed despite retry; set loglevel to DEBUG to see all exceptions. Last exception message from "Configuration PID 294, script[0]" was: Failed to set ACL (java.lang.IllegalStateException: No JackrabbitAccessControlList available for path /foo) AclLine ALLOW {principals=[principal], privileges=[jcr:read]}
> {noformat}
>  
> The first WARN message hints into the correct direction, but it could be clearer (on the code side it's already clear that there is not ACL tree, but a child tree with the name 'rep:policy').
> (Not sure if the exception message can be improved as well.)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)