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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2013/11/08 08:05:17 UTC

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

     [ https://issues.apache.org/jira/browse/OAK-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra resolved OAK-946.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.11

Initial planned work done on this. Any further improvement in debugging would be tracked with separate issue

> 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
>             Fix For: 0.11
>
>         Attachments: OAK-946-2-updated.patch, OAK-946-2.patch, 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 was sent by Atlassian JIRA
(v6.1#6144)