Thanks a lot Mladen, I really appreciate your help. About the AJP leaving connections open; If you hadn't @apache.org in your email address I wouldn't believe you ;)
2010/10/26, Mladen Turk <mt...@apache.org>: > On 10/26/2010 08:36 PM, Marc Wilmots wrote: >> >> 1200> 1000, thus your theory is probably right. > > :) > >> However, I'm just >> wondering... I read that when Tomcat reaches the max number of >> connections, >> just rejects new connections (I'm omitting the backlog on purpose). >> >> So, I can understand that my Tomcat is reaching the maxThreads, but I'm >> supposing that once I stop my stress test, the connections should go down, >> and not remain there as "idle" as they do now. No load, means no more >> connections, so why does mod_jk keep the 200 connections occupied? I don't >> have anything set such as keepalive or whatever.. Shouldn't it just >> release >> the connections? >> > > Simple. AJP is constant protocol. Once established the > connections are never released but rather reused. > Well unless you set the connectionTimeout which basically > is not "connection" timeout but rather the timeout > between 2 http requests made over the persistent connection. > > > Regards > -- > ^TM > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
