When I run Tomcat 5.5 with APR the min/maxSpareThread attributes don't appear to be working. maxThreads works fine however. Here's the details:

Versions:
Tomcat 5.5.16
APR 1.2.6
Native Connector 1.1.2
Sun's JDK 1.5.0_06
RedHat AS3

With APR:
server.xml:
<Connector port="4443" maxHttpHeaderSize="8192" address="10.0.111.47" maxThreads="50" minSpareThreads="15" maxSpareThreads="25"
               enableLookups="false" disableUploadTimeout="true"
               acceptCount="100" scheme="https" secure="true"
               SSLEngine="on"
               SSLCertificateFile="${catalina.base}/conf/x4j2ee.crt"
SSLCertificateKeyFile="${catalina.base}/conf/ x4j2ee.key" />

catalina.out:
Apr 18, 2006 10:19:16 AM org.apache.coyote.http11.Http11AprProtocol start
INFO: Starting Coyote HTTP/1.1 on http-10.0.111.47-4443

/manager/status:
                             http-10.0.111.47-4443

   Max threads: 50 Min spare threads: 0 Max spare threads: 0 Current
   thread count: 1 Current thread busy: 1 Keeped alive sockets count: 0

I also verified that this wasn't just a problem with the manager app's reporting. Doing a thread dump (kill -3) on the PID showed only 3 threads associated with the http-10.0.111.47-4443 connector (a Poller, an Acceptor and a "-1" thread). I can also change the maxThreads value and that update is reflected in the manager's status page.

Without APR:
server.xml:
<Connector port="4443" maxHttpHeaderSize="8192" address="10.0.111.47" maxThreads="50" minSpareThreads="15" maxSpareThreads="25"
               enableLookups="false" disableUploadTimeout="true"
               acceptCount="100" scheme="https" secure="true"
               sslProtocol="TLS" />

catalina.out:
Apr 18, 2006 10:14:17 AM org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-10.0.111.47-4443

/manager/status:
                             http-10.0.111.47-4443

   Max threads: 50 Min spare threads: 15 Max spare threads: 25 Current
   thread count: 15 Current thread busy: 1

Again, I verified with a thread dump that without APR enabled I see threads "http-10.0.111.47-4443-Processor1" to "http-10.0.111.47-4443- Processor15".

Known bug?  Configuration problem I missed?

The example shown at http://tomcat.apache.org/tomcat-5.5-doc/apr.html includes the min/maxSpareThreads attributes.

Thanks,
-adam

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to