[Bug 62395] After applying 7.0.88 the minSpareThreads setting does not appear to be implemented

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=62395

--- Comment #4 from Kim Walsh  ---
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?

-- 
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

[Bug 62395] After applying 7.0.88 the minSpareThreads setting does not appear to be implemented

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=62395

Mark Thomas  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Mark Thomas  ---
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.

-- 
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

[Bug 62395] After applying 7.0.88 the minSpareThreads setting does not appear to be implemented

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=62395

--- Comment #2 from Kim Walsh  ---
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

-- 
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

[Bug 62395] After applying 7.0.88 the minSpareThreads setting does not appear to be implemented

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=62395

--- Comment #1 from Mark Thomas  ---
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