[SLING-1047] Using DefaultAccessManager fills up log

• Type: Improvement
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: JCR Jackrabbit Server 2.0.6
• Fix Version/s: JCR Jackrabbit Server 2.0.6
• Assignee: Unassigned
• Reporter: Marc
• Created: 14/Jul/09 16:29
• Updated: 17/Feb/10 08:01
• Resolved: 07/Nov/09 00:55

Description

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.