WildFly JBossWeb Tomcat Connector Internal ThreadPool Statistics: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
Line 9: Line 9:
=Overview=
=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 on ([[standalone.conf]] or in domain.conf).
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>

Revision as of 17:40, 10 May 2017

Internal

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):

JAVA_OPTS="${JAVA_OPTS} -Dorg.apache.tomcat.util.ENABLE_MODELER=true"

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

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