Summary: | After applying 7.0.88 the minSpareThreads setting does not appear to be implemented | ||
---|---|---|---|
Product: | Tomcat 7 | Reporter: | Kim Walsh <walshkim> |
Component: | Connectors | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 7.0.88 | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | AIX |
Description
Kim Walsh
2018-05-21 13:27:56 UTC
I think this is a documentation issue. The meaning on minSpareThreads probably isn't what a reader of the documentation would think it is. minSpareThreads sets the minimum number of threads that will be kept in the pool, regardless of how busy it is. It is not the minimum number of idle threads that will be maintained by the pool. The meaning of this attribute has changed over time. Back in the 4.1.x era, it did mean the number of idle threads maintained in the pool. It looks like the docs haven't kept up. Changing the name of the attribute is an option, but that will create migration issues. I'm leaning towards better docs. Hi Mark, So do you have any idea why in the jump from 7.0.82 to 7.0.88 the total available threads has dropped so significantly? Thanks Kim Docs updated in: - trunk for 9.0.9 onwards - 8.5.x for 8.5.32 onwards - 8.0.x for 8.0.53 onwards - 7.0.x for 7.0.89 onwards Regarding the specific numbers, there are lots of possible explanations. The users list is the place to explore those. Hi Mark, I'm not sure how the users list works - is there a page that gives me information? This is clearly a change in behaviour - could it be that threads are returned to the pool much quicker than they used to be? |