DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31227>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31227 org.apache.tomcat.util.threads.ThreadPool MAX_THREADS_MIN value too high. Summary: org.apache.tomcat.util.threads.ThreadPool MAX_THREADS_MIN value too high. Product: Tomcat 4 Version: 4.1.30 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Connector:Coyote HTTP/1.1 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The org.apache.tomcat.util.threads.ThreadPool.adjustLimits() method denies a "maxProcessors" (maxThreads) value less than that established by the (class private) constant MAX_THREADS_MIN variable. MAX_THREADS_MIN is hardwired to a value of 10. The adjustLimits() method therefore forces a minimum of 10 threads, providing servicing of up to 9 concurrent connections. This is problematic in some deployment scenarios where support for a very limited number of concurrent connections is desired due to resource and/or other limitations. While all of the other "sanity" checks and corresponding value adjustments in the adjustLimits() method appear reasonable, the MAX_THREADS_MIN value seems simply arbitrary. I have tested a ThreadPool variant with MAX_THREADS_MIN = 2 and managed to run Tomcat V4.1.30 configured to service a single connection with no apparent ill effects (beyond the occasional warning message). IMHO, the MAX_THREADS_MIN value should be set to 2. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
