Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 77518 invoked from network); 15 Dec 2009 16:04:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Dec 2009 16:04:14 -0000 Received: (qmail 85940 invoked by uid 500); 15 Dec 2009 16:04:10 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 85841 invoked by uid 500); 15 Dec 2009 16:04:09 -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 85830 invoked by uid 99); 15 Dec 2009 16:04:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2009 16:04:09 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [68.142.206.161] (HELO n22.bullet.mail.mud.yahoo.com) (68.142.206.161) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 15 Dec 2009 16:04:05 +0000 Received: from [68.142.194.243] by n22.bullet.mail.mud.yahoo.com with NNFMP; 15 Dec 2009 16:03:44 -0000 Received: from [67.195.9.81] by t1.bullet.mud.yahoo.com with NNFMP; 15 Dec 2009 16:03:44 -0000 Received: from [67.195.9.107] by t1.bullet.mail.gq1.yahoo.com with NNFMP; 15 Dec 2009 16:03:43 -0000 Received: from [127.0.0.1] by omp111.mail.gq1.yahoo.com with NNFMP; 15 Dec 2009 16:03:43 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 843995.35592.bm@omp111.mail.gq1.yahoo.com Received: (qmail 1463 invoked by uid 60001); 15 Dec 2009 16:03:43 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1260893023; bh=fokahCOO+pb72gZeX4wy9C+qxAqDOpgb1BSjmbu4gfQ=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=T7+7oOmOAWpiJL2fUIBODROZ9Rk/PzP3qXbpzHSLx6sqiAdX/jC2pPUMeioQ//XeLnQx+A8/LPqS2yJsBx8h3wZ64GNgYfvKmMqczaFZ1uxPzfHEXwRNi80j5KXSoqTX8fnFlfGZc5WqYW96W2zErZ0VTJnm+5MVYFkHfX4kaG8= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=dXJ773peXyzsTS53LmE1P9YiOIWJWKjH2/JBPhF/oY9YMTeoqHpljZ7LNiSKI7SNSqeLraCl0nr2YVICvR6gkVfh2ERu400nGD62g4b9+n/ez9fkZKx1hGJXRXuoh+UEqfUOMoZmCt2kMeG83MJ9pl8lkVSlCK7udRnQXAhCZ0g=; Message-ID: <740354.95122.qm@web111811.mail.gq1.yahoo.com> X-YMail-OSG: N42_dtMVM1l_FBYFuAUy0NJ0BYUkyti5f_060EVG9gGWNFyktF0W_AjyN_VdMdeNI_a4JjNFveADbXS9OA5nmZBGy.1eb_cK3cTFjVWMaQ1NA47kjHhzEijra3S4ZX4da9e4hkUzoEzERUXiRr7RZRsN3l98YIhOJKAQMV39wz53cINU.GGM2Hfwj9XNEnWnEelTIiu2OuBb7OYNywaoaEVUWIuP1UViDeM8QtkD_90P4vLYuOFqDXbTToa5suw_mNA- Received: from [12.28.210.132] by web111811.mail.gq1.yahoo.com via HTTP; Tue, 15 Dec 2009 08:03:43 PST X-Mailer: YahooMailRC/240.3 YahooMailWebService/0.8.100.260964 Date: Tue, 15 Dec 2009 08:03:43 -0800 (PST) From: Chetan Chheda Subject: Limit user sessions in tomcat To: users@tomcat.apache.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1011192104-1260893023=:95122" --0-1011192104-1260893023=:95122 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hello, =0A=0A=A0=A0=A0 We frequently have situations where a user=A0has bro= ught=A0down a tomcat entirely by himself by running the same transaction mu= ltiple times because the response was not quick enough. =0A=0A=A0 Is there = a way through configuation of tomcat and mod_jk to control the number of co= ncurrent transactions/sessions a user can maintain? Since this is something= that can happen to anyone out there, I am curious as to how you are handli= ng this scenario..=0A=0AThanks,=0AChetan=0A=0A=0A --0-1011192104-1260893023=:95122--