On 26/10/2011 16:55, Rohit Kelapure wrote: > Is this because we are never quite sure as to when *all* of the > threads in the pool have been renewed ?
I assume so, yes. > 2. Does the thread renewal approach scale under load (i.e. all threads > in the pool busy servicing requests and CPU close to 90%) ? Don't know. It hasn't been tested. Looking at when it tests for renewal it should only ever do it when there is some slack. > Is it meant for production deployments ? Will it work? Yes. Would you be better off fixing whatever memory leak means you need to use this in the first place. Absolutely yes. > 3. How about threads that are servicing long running HTTP Keep-alive > connections that never let the thread return to the pool. Are these > threads renewed before the server is stopped. If the threads are never returned then they will never be renewed. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
