[
https://issues.apache.org/jira/browse/SLING-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738936#action_12738936
]
Vidar S. Ramdal commented on SLING-1047:
----------------------------------------
You're right about rev#790290. My guess is that repository.xml should not have
been committed, so that PluggableDefaultAccessManager should not be set as
default. I'll take this to the mailing list.
> Using DefaultAccessManager fills up log
> ---------------------------------------
>
> Key: SLING-1047
> URL: https://issues.apache.org/jira/browse/SLING-1047
> Project: Sling
> Issue Type: Improvement
> Affects Versions: JCR Jackrabbit Server 2.0.5
> Reporter: Marc
> Priority: Trivial
> Attachments: log.patch
>
>
> For security reasons, I deactivated the bundle
> org.apache.sling.jcr.jackrabbit.accessmanager. This leads to several log
> lines per repository access and makes reading the log unnecessarily
> cumbersome. PluggableDefaultAccessManager is the culprit:
> 14.07.2009 17:46:17.903 *INFO* [127.0.0.1 [1247586206587] GET
> /hugo/b/Usefull%20to%20know/ HTTP/1.1]
> org.apache.sling.jcr.jackrabbit.server.impl.AccessManagerFactoryTracker
> Registering PluggableDefaultAccessManager instance
> 14.07.2009 17:46:17.903 *WARN* [127.0.0.1 [1247586206587] GET
> /hugo/b/Usefull%20to%20know/ HTTP/1.1]
> org.apache.sling.jcr.jackrabbit.server.impl.security.PluggableDefaultAccessManager
> No pluggable AccessManager available, falling back to DefaultAccessManager
> I'm not familiar with PluggableDefaultAccessManager nor the bundle, so the
> patch might be more a problem indication than a solution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
