https://bz.apache.org/bugzilla/show_bug.cgi?id=68934
Remy Maucherat <r...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Remy Maucherat <r...@apache.org> ---
It is not possible to do something generic for everything.
I added a debug log to LimitLatch when going over the limit, which is the
structure used for enforcing maxConnections. The latch had some tracing
already, but nothing for the actually important event ... This could get
verbose if hit all the time though.
maxThreads is about the thread pool, which has a lot of statistics and
exceptions when rejecting a task (when maxThreads + queue full). There are
multiple possible thread pool implementations so any of them could be doing
something slightly different.
--
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
