[
https://issues.apache.org/jira/browse/SLING-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762205#action_12762205
]
Ian Boston commented on SLING-1047:
-----------------------------------
I think the error message is probably a symptom of something in else going
wrong further down the stack. If, for instance, one of the components that the
access manager depends on fails to start correctly this message will be emitted
every time the access manager is accessed (ie whenever you do anything in jcr.)
> 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.
