on - edited on by
MaciejNeumann
Abstract
This troubleshooting guide will help you understand why the JMX extension is stuck in a Pending state.
Problem
Once a JMX extension is installed, it will take a few minutes to activate its metrics and finally reach an OK state. However, sometimes this doesn't happen, and the extension remains in a Pending status even after some time. There might be different reasons behind this.
A tool that will help with troubleshooting is the JConsole.
Troubleshooting steps
The most frequent issue is that the OneAgent feature Java Metric Extensions 2.0 (JMX) [Opt-In] hasn't been activated. This can be verified at the process group level or globally in the main settings.
After enabling this feature, the process which we want to gather metrics from, MUST be restarted.
If the two above conditions are met, it might be that the process we want to monitor for the connection pool doesn't expose the needed MBeans.
What are the needed MBeans?
each JMX extension needs different MBeans to build metrics:
- For Tomcat we expect MBeans under Catalina domain and DataSource type
- For WebSphere we expect MBeans under WebSphere domain and ConnectionPoolStats type
- For Jboss we expect Mbeans under jboss.as domain and subsystem=datasources
- For IBM WebSphere Liberty we expect Mbeans under WebSphere domain and type (ThreadPoolStats,ServletStats,JvmStats,RequestTimingStats)
- For WebLogic we excpect Mbeans under com.bea domain and type (JDBCDataSourceRuntime,JDBCOracleDataSourceRuntime,weblogic.j2ee.descriptor.wl.JDBCConnectionPoolParamsBean)
- For Kafka we expect Mbeans under kafka.serwer , kafka.producer , kafka.consumer , kafka.connector , kafka.network , kafka.controller , kafka.log , kafka.connect domains.
- For ActiveMQ Classic we expect Mbeans under org.apache.activemq domain and type=Broker
- For Eclipse Jetty we expect Mbeans under :
org.eclipse.jetty.util.thread domain and type=queuedthreadpool
org.eclipse.jetty.server.handler domain and type=statisticshandler
org.eclipse.jetty.server:context=* domain and type=connectorstatistics - Mbeans for custom extensions are defined in the extension.yaml
How to check if those MBeans are correctly exposed?
This can be checked through the usage of JConsole. In this tool, open the process you want to monitor and navigate to the MBeans tab:
In this console, we can see the Mbean under jboss.as domain with subsystem=logging.
Cross check the MBeans in the JConsole with the one needed listed above.
What's next
Please reach out to support if this article does not help. In the support ticket, please provide:
- Agent support archive of the Host where the monitored process run
- ID of the host and the process
- Screenshots from the JConsole
- MBeans missing
