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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2013/08/09 10:48:47 UTC

[jira] [Commented] (OAK-946) Improve support for debugging Oak

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

Michael Dürig commented on OAK-946:
-----------------------------------

The current approach would lead to duplicate identifiers across restarts and also across different cluster nodes. As these identifiers tend to go into log files we should probably make sure they are not ambiguous. One way to do that is by prefixing them with a repository id, which would be unique for the repository and a start up time stamp, which would be unique across restarts. The repository id could either be (or default to) a uuid and/or be configurable.
                
> Improve support for debugging Oak
> ---------------------------------
>
>                 Key: OAK-946
>                 URL: https://issues.apache.org/jira/browse/OAK-946
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: core, jcr
>    Affects Versions: 0.8
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>         Attachments: OAK-946.patch
>
>
> To simplify diagnosing Oak related issues and also runtime debugging we should have some inbuilt support in Oak
> * Way to uniquely identify session, ContentSession and SessionDelegate
> * Look into possibility of exposing session as SLF4j Marker [1] instance while logging
> [1] http://stackoverflow.com/questions/4165558/best-practices-for-using-markers-in-slf4j-logback

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