[
https://issues.apache.org/jira/browse/JCR-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-2736.
--------------------------------
Assignee: Jukka Zitting
Fix Version/s: 2.2.0
Resolution: Fixed
I changed the log level to debug in revision 1000420. The exceptions are in any
case thrown to the client application, so logging these cases as warnings seems
excessive.
> Exception messages in AuthorizableImpl include full tracebacks at warn level.
> -----------------------------------------------------------------------------
>
> Key: JCR-2736
> URL: https://issues.apache.org/jira/browse/JCR-2736
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.1.1
> Reporter: Ian Boston
> Assignee: Jukka Zitting
> Fix For: 2.2.0
>
>
> In a number of places in AuthourizableImpl there are log.warn with tracebacks.
> This would be fine, however in production with Sling its quite easy to
> attempt to set a property on the Authorizable and generate the traceback in
> the logs, which soon fill up.
> We could block all logging from the user manager, but that feels wrong.
> Would it be possible to have the log message at warn level put out a single
> log line and at debug level put out the full traceback ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
