You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2010/01/07 23:25:47 UTC

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

https://issues.apache.org/bugzilla/show_bug.cgi?id=44571

--- Comment #2 from Tim Whittington <Ti...@orionhealth.com> 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 to specify a timeout for threads to
obtain a connection when the pool is full.

The only thing that might be worth changing is the response code when an
endpoint cannot be obtained for a mapped worker - Currently this produces a
500, whereas a HTTP_STATUS_SERVICE_UNAVAIL (503) would be more appropriate.

-- 
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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org