jmx,jconsole学习心得

2017-08-24 本文已影响59人赤子心_d709

背景

之前看zk代码的时候，一直不清楚jmv是干啥的,去学习了一下
主要学习了
http://blog.csdn.net/u013256816/article/details/52840067 以及《jmx in action》

感受

关于场景使用

现在有什么场景会有jmx相关的需求？分监控以及管理思考。

监控

自己写jmx，定义Mbean，给外部暴露信息，似乎需求不是那么强烈，打日志就能解决。
或者暴露接口支持http请求等。

管理

就是动态的设置一个值，业务场景上，这个功能有点类似于中心配置化。
中心配置化也可以不用JMX完成，至少ZOOKEEPER可以办到吧？

后续

学习了这一块之后，让我对下面几块感兴趣

死锁检测

http://docs.oracle.com/javase/7/docs/technotes/guides/management/jconsole.html
这个里面的这一段感兴趣，定位死锁的，目前看了下也没有特别好的demo可以参考，自己可以写个死锁然后用JMX方式来检测一下

The Threading MXBean provides several other useful operations that are not covered by the Threads tab.
findMonitorDeadlockedThreads
: Detects if any threads are deadlocked on the object monitor locks. This operation returns an array of deadlocked thread IDs.

getThreadInfo
: Returns the thread information. This includes the name, stack trace, and the monitor lock that the thread is currently blocked on, if any, and which thread is holding that lock, as well as thread contention statistics.

getThreadCpuTime
: Returns the CPU time consumed by a given thread

You can access these additional features via the MBeans tab by selecting the Threading MXBean in the MBeans tree. This MXBean lists all the attributes and operations for accessing threading information in the Java VM being monitored. See [Monitoring and Managing MBeans](http://docs.oracle.com/javase/7/docs/technotes/guides/management/jconsole.html#gdeap).