On 15.07.2011 12:09, Edward Quick wrote: > Thanks for your replies. I found the solution was to set JkWatchdogInterval > (by default this is not on). I set it to 30, and observed the FIN_WAIT > disappears after 60 seconds (this could be the worker.maintain setting?) and > the CLOSE_WAIT thread disappeared when it reached the connection_pool_timeout. > > Does this mean connection_pool_timeout only works if JkWatchdogInterval is > swithed on?
No, it would also be checked, if a process gets a rquest to handle. So if there is traffic it usually works fine without the watchdog thread. But since pools are per process and we can't assume that each of the processes with idle connections will get new requests soon, t is usually better to switch on the watchdog. Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
