jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bart van der Schans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3426) Log warning when changes are performed with event notification thread
Date Mon, 17 Sep 2012 16:07:07 GMT

    [ https://issues.apache.org/jira/browse/JCR-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457112#comment-13457112
] 

Bart van der Schans commented on JCR-3426:
------------------------------------------

If there are valid (exceptional) use cases for using the notification thread to make changes,
then logging the full stack trace on WARN might be a bit too verbose. In that case we might
consider logging the full stack only on debug level with a reference to it in the warning
with something like: "full stack trace available on debug"
                
> Log warning when changes are performed with event notification thread
> ---------------------------------------------------------------------
>
>                 Key: JCR-3426
>                 URL: https://issues.apache.org/jira/browse/JCR-3426
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>         Attachments: JCR-3426.patch
>
>
> Using the event notification thread (this is the thread calling the
> onEvent() method of an EventListener implementation) to perform changes
> on the repository is dangerous because it is a rather expensive call
> and may cause the event queue to fill up. I think it would be good if
> the repository logs a warning with a stack trace in this case.

--
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

Mime
View raw message