[
https://issues.apache.org/jira/browse/SLING-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773710#action_12773710
]
Ian Boston commented on SLING-1170:
-----------------------------------
We probably don't need the warn, but if you are trying to plug something in and
it doesn't work, then having the warn there can eliminate frustrations. It also
gives anyone on dev@ the opportunity to say "did you see
.PluggableDefaultAccessManager No pluggable AccessManager available " in your
logs, when the inevitable question comes "why doesn't this work"
wdyt?
(can easilly downgrade to debug, not a problem)
> Log is spammed by pluggable default access manager
> --------------------------------------------------
>
> Key: SLING-1170
> URL: https://issues.apache.org/jira/browse/SLING-1170
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Jackrabbit Server 2.0.5
> Reporter: Carsten Ziegeler
> Assignee: Ian Boston
> Fix For: JCR Jackrabbit Server 2.0.5
>
>
> Currently the log is spammed on every request with these messages:
> 04.11.2009 13:32:51.309 *INFO* [127.0.0.1 [1257370371287] GET
> /slingshot/albums/travel.html HTTP/1.1]
> org.apache.sling.jcr.jackrabbit.server.impl.AccessManagerFactoryTracker
> Registering PluggableDefaultAccessManager instance
> 04.11.2009 13:32:51.309 *WARN* [127.0.0.1 [1257370371287] GET
> /slingshot/albums/travel.html HTTP/1.1]
> org.apache.sling.jcr.jackrabbit.server.impl.security.PluggableDefaultAccessManager
> No pluggable AccessManager available,
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
