--- title: Application server JMX setup source: https://docs.newrelic.com/docs/apm/agents/java-agent/troubleshooting/application-server-jmx-setup --- ## Problem In APM, the **Threads** tab on the [**JVMs** page](https://docs.newrelic.com/docs/agents/java-agent/features/jvm-metrics-page) shows various JMX metrics supported by your application server, such as active, idle and total threads. In order to see metrics in the **Threads** tab, you must enable JMX reporting in your application server. If JMX reporting is not enabled you will see an empty **Threads** tab with a link to relevant documentation for your application server to enable JMX. ## Solution To resolve the issue, read the following sections depending on your application server: **JBoss** Local support for JMX is enabled on JBoss Application servers by default. If you have changed the default settings, see: - [JBoss EAP 6.0](https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Administration_and_Configuration_Guide/index.html) - [JBoss AS 7.1](https://docs.jboss.org/author/display/AS71/Admin%20Guide.html#8094211_AdminGuide-JMX) - [JBoss AS 6](https://docs.jboss.org/jbossas/6/Admin_Console_Guide/en-US/html/) **Jetty** To enable local support for JMX on Jetty Application servers, configure the MBeanContainer with the **etc/jetty-jmx.xml** file. For more information, see: - [Jetty 7 and 8](http://wiki.eclipse.org/Jetty/Tutorial/JMX) - [Jetty 9](http://www.eclipse.org/jetty/documentation/current/jmx-chapter.html) **Glassfish** While local support for JMX is enabled on Glassfish Application servers by default, the MBeans which actually provide metric information default to `OFF`. For the appropriate metrics to be gathered by the application server, the following components must be set in the **Monitoring Service**: - [Glassfish 4.x](https://glassfish.java.net/docs/4.0/administration-guide.pdf): The Web Container, HTTP Service, and Transaction Service components must be set to the HIGH monitoring level. - [Glassfish 3.1](http://docs.oracle.com/cd/E18930_01/html/821-2416/ablur.html): The Web Container, HTTP Service, and Transaction Service components must be set to the HIGH monitoring level. - [Glassfish 3.0](http://docs.oracle.com/cd/E19798-01/821-1751/ablvr/index.html): The Web Container, Thread Pool, and Transaction Service components must be set to the LOW monitoring level. - [Glassfish 2.1](http://docs.oracle.com/cd/E19879-01/820-4335/ablur/index.html): The Web Container, Thread Pool, and Transaction Service components must be set to the LOW monitoring level. **Resin** Local support for JMX is enabled on Resin Application servers by default. If you have changed the default settings, see: - [Resin 3.1](http://www.caucho.com/resin-3.1/doc/resin-admin.xtp#JMXInstrumentingBeans) - [Resin 4.0](http://www.caucho.com/resin-4.0/admin/advanced-jmx.xtp) **Tomcat** Local support for JMX is enabled on Tomcat Application servers by default. If you have changed the default settings, see: - [Tomcat 5.5](http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html) - [Tomcat 6](http://tomcat.apache.org/tomcat-6.0-doc/monitoring.html) - [Tomcat 7](http://tomcat.apache.org/tomcat-7.0-doc/monitoring.html) - [Tomcat 8](https://tomcat.apache.org/tomcat-8.0-doc/monitoring.html) - [Tomcat 9](http://tomcat.apache.org/tomcat-9.0-doc/monitoring.html) **Tomcat EE** Local support for JMX is enabled on TomEE Application servers by default. If you have changed the default settings, see: - [TomEE 1.5](http://tomee.apache.org/documentation.html) **WebLogic** Local support for JMX is enabled on WebLogic Application servers by default. If you have changed the default settings, see: - [WebLogic 12](http://docs.oracle.com/cd/E24329_01/web.1211/e24415/toc.htm) - [WebLogic 11](http://docs.oracle.com/cd/E23943_01/web.1111/e13728/toc.htm) - [WebLogic 10](http://docs.oracle.com/cd/E12840_01/wls/docs103/jmx/index.html) **WebSphere** Local support for JMX is **disabled** on WebSphere Application servers by default. For more information, see: - [WebSphere 9](https://www.ibm.com/support/knowledgecenter/SSEQTP_9.0.0/com.ibm.websphere.base.doc/ae/csec_rsecmgr2.html) - [WebSphere 8.5](https://www.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.base.doc/ae/csec_rsecmgr2.html) - [WebSphere 7](https://www.ibm.com/support/knowledgecenter/SSEQTP_7.0.0/com.ibm.websphere.base.doc/info/aes/ae/csec_rsecmgr2.html) And the related New Relic documentation: - [Enable WebSphere PMI metrics](https://docs.newrelic.com/docs/agents/java-agent/features/jvm-metrics-page#default-pmi) **WebSphere Liberty** Local support for JMX is **disabled** on WebSphere Application Liberty servers by default. For more information, see: - [WebSphere 16+](https://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/cwlp_java2security.html) - [WebSphere 8.5](https://www.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.wlp.core.doc/ae/cwlp_java2security.html) **WildFly** Local support for JMX is enabled on WildFly Application servers by default. If you have changed the default settings, see: - [WildFly 21.0.0](https://docs.wildfly.org/21/Admin_Guide.html#JMX)