[jira] [Commented] (JCR-2961) Improve logging of Session.save() to trace back root cause of externally modified nodes

["Thomas Mueller (JIRA)" <ji...@apache.org>]

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

Thomas Mueller commented on JCR-2961:
-------------------------------------

To enable logging  each session.save call, configure the logger (logback) as follows (logs to stdout):

  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
    <layout class="ch.qos.logback.classic.PatternLayout">
      <Pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</Pattern>
    </layout>
  </appender>

  <logger 
      name="org.apache.jackrabbit.core.session.SessionSaveOperation" 
      level="DEBUG">
    <appender-ref ref="STDOUT"/>
  </logger>

If the system property "org.jackrabbit.logWithStackTrace" is set to "true", then a stack trace is logged as well (this slows down performance).

> Improve logging of Session.save() to trace back root cause of externally modified nodes
> ---------------------------------------------------------------------------------------
>
>                 Key: JCR-2961
>                 URL: https://issues.apache.org/jira/browse/JCR-2961
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>            Priority: Minor
>             Fix For: 2.3.0
>
>
> Currently it's very difficult to find the root cause of error like: javax.jcr.InvalidItemStateException: <UUID> has been modified externally.
> To better trace back such issues, it would be nice to add DEBUG logging for the Session.save() call.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira