You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Tom Barber (JIRA)" <ji...@apache.org> on 2014/12/13 22:41:13 UTC
[jira] [Updated] (OODT-774) Introduce MX4J monitoring for JMX
PushPull Daemons
[ https://issues.apache.org/jira/browse/OODT-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Barber updated OODT-774:
----------------------------
Fix Version/s: (was: 0.8)
0.9
Push to 0.9
> Introduce MX4J monitoring for JMX PushPull Daemons
> --------------------------------------------------
>
> Key: OODT-774
> URL: https://issues.apache.org/jira/browse/OODT-774
> Project: OODT
> Issue Type: Improvement
> Components: push pull framework
> Affects Versions: 0.7
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Fix For: 0.9
>
>
> I have been working with MX4J (0) for a while (1) for monitoring daemons and I think it is a great tool. Being able to monitor pushpull client daemons would be an improvement for managing and analyzing this particular OODT component from an automated standpoint.
> I propose to implement MX4J monitoring for running daemons in an attempt to learn more about behavior of running deamon Threads.
> (0) http://mx4j.sourceforge.net/
> (1) https://issues.apache.org/jira/browse/CASSANDRA-6518
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)