[
https://issues.apache.org/jira/browse/OAK-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055030#comment-14055030
]
Rob Ryan edited comment on OAK-941 at 7/8/14 3:38 PM:
------------------------------------------------------
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.
Update: in JDK 1.7b55 the implementation changed and the hotspot moved but the
problem is the same. The new hotspot is
java.util.concurrent.FutureTask.report(int).
was (Author: [email protected]):
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)