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 2016/02/10 15:51:18 UTC

[jira] [Resolved] (OAK-3718) JCR observation should be visible in SessionMBean

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

Michael Dürig resolved OAK-3718.
--------------------------------
    Resolution: Not A Problem

As indicated, all relevant information should be there already.

> JCR observation should be visible in SessionMBean
> -------------------------------------------------
>
>                 Key: OAK-3718
>                 URL: https://issues.apache.org/jira/browse/OAK-3718
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.0.24
>            Reporter: Jörg Hoh
>              Labels: monitoring, observation, resilience
>             Fix For: 1.4
>
>
> I am looking for long-running sessions, which are not (explicitly or implicitly) refreshed. As the a session, which has a registered JCR observation event listener, gets refreshed implicitly, it would be good to see in the Session MBean, if a JCR observation event handler is registered for this session.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)