You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2013/05/16 12:17:16 UTC

[jira] [Resolved] (JCR-3595) AbstractJournal logging is too verbose

     [ https://issues.apache.org/jira/browse/JCR-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved JCR-3595.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.7.1
                   2.6.2
         Assignee: Jukka Zitting

Fixed in revision 1483286. Backported to 2.6 in revision 1483291.
                
> AbstractJournal logging is too verbose
> --------------------------------------
>
>                 Key: JCR-3595
>                 URL: https://issues.apache.org/jira/browse/JCR-3595
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.6.1, 2.7
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 2.6.2, 2.7.1
>
>
> The AbstractJournal class often logs a lot of INFO messages when syncing up with the journal. Since the information value of these log entries is pretty low for normal use and they occur pretty often, having them at DEBUG level would be more appropriate.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira