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 "Rob Ryan (JIRA)" <ji...@apache.org> on 2014/07/08 17:13:05 UTC
[jira] [Commented] (OAK-941) MBean to track sessions
[ https://issues.apache.org/jira/browse/OAK-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055030#comment-14055030 ]
Rob Ryan commented on OAK-941:
------------------------------
I'll will be filing a bug that the current implementation of the registration/unregistration of the mbean introduces a performance bottleneck in logout where com.google.common.util.concurrent.Futures.addCallback(ListenableFuture, FutureCallback) is used this results in excessive time spent in java.util.concurrent.FutureTask$Sync.innerGet(). This occurred with jdk 1.7b25. I will recheck with jdk1.7b55 to see if that is a viable workaround as the FutureTask implementation has changed.
> MBean to track sessions
> -----------------------
>
> Key: OAK-941
> URL: https://issues.apache.org/jira/browse/OAK-941
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core, jcr
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Labels: monitoring
> Fix For: 0.15
>
>
> Create JMX MBean to track Session and session related information:
> * stack trace from where the session has been acquired,
> * age of the session,
> * last (read/write) access to the session,
> * last refresh of the session,
> * conflict information (e.g. unresolved conflicts),
> * session attributes,
> * ...
--
This message was sent by Atlassian JIRA
(v6.2#6252)