View source for WildFly JBossWeb Tomcat Connector Internal ThreadPool Statistics

=Internal=

* [[JBossWeb_Monitoring#Tomcat_Connector_Internal_ThreadPool_Statistics|JBossWeb Monitoring]]

=Relevance=

* EAP 6.4.10

=Overview=

Tomcat connector internal thread pool JMX statistics are not exposed by default. In order to expose them, the JBoss instance must start with "org.apache.tomcat.util.ENABLE_MODELER" system property set to "true". This can be done in the .conf file corresponding to the mode JBoss is run in (standalone.conf or in domain.conf):

<pre>
JAVA_OPTS="${JAVA_OPTS} -Dorg.apache.tomcat.util.ENABLE_MODELER=true"
</pre>

Alternatively, it can be specified in the <system-properties> section of the configuration file:

<pre>
<system-properties>
    ...
    <property name="org.apache.tomcat.util.ENABLE_MODELER" value="true"/>
    ...
</system-properties>
</pre>

The system property will determine the Tomcat Http11Protocol or class AjpProtocol to expose the corresponding JIoEndpoit in JMX as "jboss.web:name=<protocol>-<bind-address>-<port>,type=ThreadPool". Example: "jboss.web:name=ajp-127.0.0.1-8009,type=ThreadPool".

=JMX Metrics=

===currentThreadCount====
===currentThreadsBusy====