jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-2961) Improve logging of Session.save() to trace back root cause of externally modified nodes
Date Thu, 05 May 2011 16:25:03 GMT

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

Marcel Reutegger commented on JCR-2961:
---------------------------------------

Would it be possible to put the path of the item into the exception message instead of the
UUID? I think that would be even more helpful.

> 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

Mime
View raw message