CodePudding user response:
Should be, JMX is an extension of the JVM provides interfaceCodePudding user response:
Is commonly, but if recording more detailed performance indicators, leads to enter safepoint, which reduces the online application performance:https://blog.csdn.net/zhxdick/article/details/107450858
Such as jstack, jmap print stack, print memory usage, can let the JVM into safepoint, threads can obtain stable state to collect information,
At the same time, the JMX exposed to the outside interface to collect information, such as using jvisualvm, will also involve the RPC and network consumption, as well as the JVM when busy, not to have collected information index breakpoints, these are all based on JMX external monitoring is difficult to solve,
So, it is recommended to use the JVM internal acquisition JFR, so even if the JVM is very busy, can also be collected useful information:
https://blog.csdn.net/zhxdick/category_9860048.html
CodePudding user response:
Should be, JMX is an extension of the JVM provides interfaceCodePudding user response:
I don't know. Let's see BBS