On 18/01/2017 13:02, André Warnier (tomcat) wrote: > On 18.01.2017 13:00, Mark Thomas wrote:
<snip/> >> Maybe change the first sentence to: >> >> The number of idle threads Tomcat keeps available to handle new >> requests. Note that excess idle threads are not stopped. The total >> number of threads will therefore increase over time with an upper limit >> of maxThreads. If you require excess idle threads to be stopped, use an >> Executor. >> >> Mark > > So what you are saying above, is that the "minSpareThreads" attribute in > a Connector (without Executor) is not really being ignored. > It is just the "shrinking" part of it that is not being done anymore, > since tomcat 6.0. > Is that the correct interpretation ? Yes. That was controlled by maxSpareThreads as far as I recall and that configuration option was removed. > A different question : how would one go about determining how many > resources /are/ being used by an idle thread ? (or more relevantly, by a > couple of hundred of them) A profiler is probably your best bet. I'd expect the answer to be "trivially little compared to the application doing some real work" > And yet another : > Above, you say that "Tomcat starts another 3 threads in the background". > When does that actually happen, in relation to "3 new connections arrive" ? > (or maybe without a direct relation, on some separate time schedule) However java.util.concurrent.ThreadPoolExecutor is implemented. > I realise that these are probably somewhat pernickety questions, and > maybe without much real-world practical importance. But I figure that > we may as well get to the bottom of this, while we have your expert > attention. Happy to help. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
