You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2012/07/04 09:40:34 UTC
[jira] [Updated] (JCR-3339) Log stack trace with warn message in
ObservationDispatcher
[ https://issues.apache.org/jira/browse/JCR-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated JCR-3339:
----------------------------------
Fix Version/s: 2.2.13
Merged into 2.2 branch in revision: 1357125
> Log stack trace with warn message in ObservationDispatcher
> ----------------------------------------------------------
>
> Key: JCR-3339
> URL: https://issues.apache.org/jira/browse/JCR-3339
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Marcel Reutegger
> Priority: Minor
> Fix For: 2.2.13, 2.5.1
>
>
> Currently the ObservationDispatcher only logs the toString() of the exception of an event consumer in a warn message. One needs to enable debug level for ObservationDispatcher to get the stack trace of the exception. Most of the time it's quite difficult to track down the root cause of the exception without a stack trace. Enabling debug logging after the issue occurs is also not very convenient.
> I suggest we print the stack trace of the exception with the warn message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira