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

Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/03/30 08:55:53 UTC

[jira] [Reopened] (OAK-2680) Report a full observation queue situation to the logfile

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

Chetan Mehrotra reopened OAK-2680:
----------------------------------

bq. Maybe we should better remove the logging again and provide better hooks for clients to do the logging themselves. 

Re opening the issue based on above comment. 

> Report a full observation queue situation to the logfile
> --------------------------------------------------------
>
>                 Key: OAK-2680
>                 URL: https://issues.apache.org/jira/browse/OAK-2680
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: oak-core
>    Affects Versions: 1.1.7
>            Reporter: Marc Pfaff
>            Assignee: Michael Dürig
>            Priority: Minor
>             Fix For: 1.1.8
>
>         Attachments: OAK-2680.patch
>
>
> This is a improvement request for having an explicit warning in the log file, when the BackgroundObserver's queue maximum is reached. 
> Currently, in that case, a warning is logged from the ChangeProcessor observer only. But as each observer has it's own queue, a warning from a more central place covering all observers would be helpful.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)