Why aren't minSpareThreads & maxSpareThreads displayed in the jmx console ?

Solution Verified - Updated -

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 5.1.2
  • Tomcat
    • 5.x
    • 6.x

Issue

  • The ajp connector configuration doesn't display in jmx console.
    The server.xml contains following
<Connector protocol="AJP/1.3" port="${jboss.port.ajp}" address="${jboss.bind.address}" emptySessionPath="true" enableLookups="false" connectionTimeout="20000" disableUploadTimeout="true" redirectPort="${jboss.port.ajp.redirect}" URIEncoding="UTF-8" maxThreads="200" minSpareThreads="25" maxSpareThreads="75" acceptCount="100" />

Is the problem due to jmx-console, which doesn't displayed some attributes, or a configuration problem ?

  • Do I have to configure this attributes maxThreads="150" minSpareThreads="25" maxSpareThreads="75" in the AJP connector? How ?

Resolution

The online documentation 1 shows the supported attributes for the ajp connector.

The parameters minSpareThreads and maxSpareThreads are from tomcat 5.5 which are no longer valid in Tomcat 6 (from which JBossWeb in EAP 5.x and 4.x were forked)2
Looking at the apache source3 for org.apache.coyote.http11.Http11Protocol.java the two parameters are no longer present.

  • Remove minSpareThreads as it is not a valid option.
  • Replace maxSpareThreads with maxThreads
  • Replace acceptCount with backlog . acceptCount is for the http connector.

  1. http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html ↩︎

  2. https://access.redhat.com/knowledge/solutions/23727 ↩︎

  3. http://apache.mirrors.timporter.net/tomcat/tomcat-6/v6.0.33/src/apache-tomcat-6.0.33-src.zip ↩︎

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments