[Bug 44571] Limits busy per worker to a threshold

2015-01-07 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=44571 --- Comment #4 from Rainer Jung --- I have changed my opinion. This can be configured using the connection_pool_size only for the ISAPI redirector. For the common mod_jk case, "busy" is a global counter, whereas the connection_pool_size is

[Bug 44571] Limits busy per worker to a threshold

2015-01-05 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=44571 Rainer Jung changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

DO NOT REPLY [Bug 44571] Limits busy per worker to a threshold

2010-01-07 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=44571 --- Comment #2 from Tim Whittington 2010-01-07 14:25:45 UTC --- I don't think this approach is the best way anymore. You can use connection_pool_size to limit the business of any given worker, and (since 1.2.27) connection_acquire_timeout

DO NOT REPLY [Bug 44571] Limits busy per worker to a threshold

2008-03-10 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=44571 Zealot <[EMAIL PROTECTED]> changed: What|Removed |Added Component|Connectors |Native:JK -- Conf

DO NOT REPLY [Bug 44571] Limits busy per worker to a threshold

2008-03-10 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=44571 --- Comment #1 from Zealot <[EMAIL PROTECTED]> 2008-03-10 06:28:02 PST --- Created an attachment (id=21648) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=21648) busy limit patch -- Configure bugmail: https://issues.apach