https://bz.apache.org/bugzilla/show_bug.cgi?id=62395
--- Comment #1 from Mark Thomas <ma...@apache.org> --- 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. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org