Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 35656 invoked from network); 23 Jan 2007 07:14:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Jan 2007 07:14:25 -0000 Received: (qmail 83078 invoked by uid 500); 23 Jan 2007 07:14:21 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 82095 invoked by uid 500); 23 Jan 2007 07:14:19 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 82084 invoked by uid 99); 23 Jan 2007 07:14:19 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jan 2007 23:14:19 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [207.113.241.148] (HELO iss04.interliant.com) (207.113.241.148) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jan 2007 23:14:09 -0800 Received: from EX-008.mail.navisite.com (ex-008.interliant.com [207.113.240.188]) by iss04.interliant.com (8.10.2/8.10.2) with ESMTP id l0N7Dle11798 for ; Tue, 23 Jan 2007 01:13:47 -0600 (CST) Received: from [192.168.0.168] ([89.164.17.201]) by EX-008.mail.navisite.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 23 Jan 2007 01:13:43 -0600 Message-ID: <45B5B5A6.4060601@jboss.com> Date: Tue, 23 Jan 2007 08:13:42 +0100 From: Mladen Turk Organization: JBoss Europe User-Agent: Mozilla MIME-Version: 1.0 To: Tomcat Users List Subject: Re: mod_jk replacement? References: <8481132.post@talk.nabble.com> <45B4FF5B.4060104@jboss.com> <8513072.post@talk.nabble.com> In-Reply-To: <8513072.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Jan 2007 07:13:44.0119 (UTC) FILETIME=[045BEC70:01C73EBE] X-Virus-Checked: Checked by ClamAV on apache.org JNeuhoff wrote: > Thank for your explanations. > >> >> If any part closes this (AJP) connection you will observe >> 'memory leaak', meaning thread will stay open without the >> clue the other part closed the connection. > > Maybe I mis-understood the meaning of the timeout settings because I always > thought that these would genuinely release the underlying TCP connections > (except for the connection_pool_minsize number of TCP connections). > Whenever you have connection pool setup in mod_jk it means you don't have constant connections any more. The connection pool will maintain the connections and close them by some rule (size). Now, having that you *must* have connectionTimeout="60000" in server.xml for the AJP connector so Tomcat can close his part of the connection as well. In any other case Tomcat connection will stay forever blocked in read() (Just look at the thread dump). The next request will allocate a new thread untill 200 is reached and consequtive requests will be rejected. Also, when you have connectionTimeout set you will need connect_timeout and prepost_timeout set which you have already so mod_jk can deal more effectively with sockets closed by Tomcat not depending on the OS socket timeouts. Next, your value for connection_pool_timeout is too low for any practical usage thought. Regards, Mladen. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org