in several Java processes monitored with Dynatrace there's a lot of threads with JMX timeout and my customer want to certify the Dynatrace agent is not openning any JMX connection to the monitored process.
So, the Dynatrace Agents opens JMX connections to the monitored process to get any type of information?
Solved! Go to Solution.
Did you configure any custom JMX measure for the agent(s)?
We use the Java Management Extension (JMX) to manage and monitor Java-based applications. The JMX interface invokes methods on MBeans to retrieve Performance Monitoring Infrastructure (PMI) data. AppMon supports JMX and provides an interface for third-party applications integration.
Review the below documentation.
no, we've not configured explicitly any JMX measure for any the agents. We want to confirm if the Dynatrace agent is not opening any JMX connection to the monitored process if we don't configure any JMX measure explicitly (via setting one JMX measure).
The agent lives within the JVM and has direct access to the JMX classes. Therefore it has no need to spawn threads or JMX connections.
I have seen your support case already. All the threads are named ""JMX server connection timeout Thread-x" which are not caused by AppMon agent.
Maybe caused by another software like