https://issues.apache.org/bugzilla/show_bug.cgi?id=49159
sylvain.laur...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #26074|0 |1
is obsolete| |
Attachment #26097|0 |1
is obsolete| |
--- Comment #11 from sylvain.laur...@gmail.com 2010-09-30 18:05:48 EDT ---
Created an attachment (id=26108)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=26108)
tc7 renew threads one by one in a bounded time
New patch with further improvements : now the behavior is more deterministic,
with an upper bound to the time necessary to renew all the threads of the pool.
The upper bound is something like N*max(threadKeepAliveTimeout, longestRequest
+ threadRenewalDelay). Where N is the number of threads in the pool and
longestRequest is the maximum time a request takes to be processed (of course
it depends on the application).
This is really a worst case scenario and it should be much quicker in usual
cases, something closer to max(threadKeepAliveTimeout, longestRequest).
I still have to make the threadRenewalDelay configurable (hardcoded to 1s for
now) and to propose some cleanups in WebAppClassLoader since this patch makes
the unsafe-and-disabled-by-default ThreadLocal cleaning obsolete. (it's still
interesting to introspect the ThreadLocals to detect potential leaks and warn
the user, it will help to improve libraries and applications...).
Any volunteer for a review before I continue finalizing this patch ?
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- 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
