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/12/23 11:20:52 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=13855537#comment-13855537 ]
Chetan Mehrotra commented on OAK-941:
-------------------------------------
The current approach of registering JMX Bean for every session would cause issue in application where there are many short lived sessions. Some of these issues might be cosmetic like in Sling where JMX registration is done via OSGi service registry. There would see frequent logs around services getting registered and unregistered
{noformat}
2013-12-23 15:43:05,611 INFO NA [pool-10-thread-2] com.adobe.granite.repository - Service [1323] ServiceEvent REGISTERED
2013-12-23 15:43:05,612 INFO NA [pool-10-thread-2] com.adobe.granite.repository - Service [1323] ServiceEvent UNREGISTERING
2013-12-23 15:43:18,488 INFO NA [pool-10-thread-4] com.adobe.granite.repository - Service [1324] ServiceEvent REGISTERED
2013-12-23 15:43:18,492 INFO NA [pool-10-thread-4] com.adobe.granite.repository - Service [1324] ServiceEvent UNREGISTERING
2013-12-23 15:43:18,493 INFO NA [pool-10-thread-4] com.adobe.granite.repository - Service [1325] ServiceEvent REGISTERED
2013-12-23 15:43:18,495 INFO NA [pool-10-thread-4] com.adobe.granite.repository - Service [1325] ServiceEvent UNREGISTERING
2013-12-23 15:43:18,496 INFO NA [pool-10-thread-4] com.adobe.granite.repository - Service [1326] ServiceEvent REGISTERED
2013-12-23 15:43:18,497 INFO NA [pool-10-thread-4] com.adobe.granite.repository - Service [1326] ServiceEvent UNREGISTERING
2013-12-23 15:43:18,497 INFO NA [pool-10-thread-4] com.adobe.granite.repository - Service [1327] ServiceEvent REGISTERED
2013-12-23 15:43:18,502 INFO NA [pool-10-thread-4] com.adobe.granite.repository - Service [1327] ServiceEvent UNREGISTERING
2013-12-23 15:43:18,503 INFO NA [pool-10-thread-4] com.adobe.granite.repository - Service [1328] ServiceEvent REGISTERED
2013-12-23 15:43:18,504 INFO NA [pool-10-thread-4] com.adobe.granite.repository - Service [1328] ServiceEvent UNREGISTERING
2013-12-23 15:43:18,505 INFO NA [pool-10-thread-4] com.adobe.granite.repository - Service [1329] ServiceEvent REGISTERED
{noformat}
Other issue is such short lived JMX object would not be of much value and would clutter the JMX namespace. Instead we should register a JMX bean if session life crosses certain threshold say more than 5 mins old. As stats from such long lived session would be more useful and would also not put load on JMX registry.
Let me know if a new issue is to be reported or we can reopen it?
> 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
> Fix For: 0.14
>
>
> 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.1.5#6160)