Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 45032 invoked from network); 6 May 2010 13:56:36 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 May 2010 13:56:36 -0000 Received: (qmail 6533 invoked by uid 500); 6 May 2010 13:56:33 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 6326 invoked by uid 500); 6 May 2010 13:56:32 -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 6314 invoked by uid 99); 6 May 2010 13:56:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 May 2010 13:56:32 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [216.82.254.211] (HELO mail201.messagelabs.com) (216.82.254.211) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 May 2010 13:56:23 +0000 X-VirusChecked: Checked X-Env-Sender: Chuck.Caldarale@unisys.com X-Msg-Ref: server-12.tower-201.messagelabs.com!1273154100!61245955!13 X-StarScan-Version: 6.2.4; banners=-,-,- X-Originating-IP: [192.61.61.105] Received: (qmail 5432 invoked from network); 6 May 2010 13:55:05 -0000 Received: from naedge.unisys.com (HELO USEA-NAEDGE2.unisys.com) (192.61.61.105) by server-12.tower-201.messagelabs.com with RC4-SHA encrypted SMTP; 6 May 2010 13:55:05 -0000 Received: from usea-nahubcas1.na.uis.unisys.com (129.224.76.114) by USEA-NAEDGE2.unisys.com (192.61.61.105) with Microsoft SMTP Server (TLS) id 8.1.393.1; Thu, 6 May 2010 08:55:05 -0500 Received: from USEA-EXCH8.na.uis.unisys.com ([129.224.76.42]) by usea-nahubcas1.na.uis.unisys.com ([129.224.76.114]) with mapi; Thu, 6 May 2010 08:55:00 -0500 From: "Caldarale, Charles R" To: Tomcat Users List Date: Thu, 6 May 2010 08:55:00 -0500 Subject: RE: JMX and Tomcat-Queue Thread-Topic: JMX and Tomcat-Queue Thread-Index: AcrtIa4zrEqrq3V/SxOgCjg5EsHC8gAAW9Gw Message-ID: <99C8B2929B39C24493377AC7A121E21F98E46DE68B@USEA-EXCH8.na.uis.unisys.com> References: <99C8B2929B39C24493377AC7A121E21F98E4690040@USEA-EXCH8.na.uis.unisys.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 > From: Baba [mailto:baba.th@googlemail.com] > Subject: Re: JMX and Tomcat-Queue >=20 > Is there no way to get this information (How much requests are in the > accept queue?) out? No, the accept queue is completely invisible. Only the comm stack knows an= ything about it, and there are no APIs I'm aware of to queue the contents -= because the content hasn't been received yet, only the connection request. I think the only way to do what you want is to increase the maxThreads valu= e, set acceptCount to something very small, and run a filter against each i= ncoming request to see if you want to process it immediately, queue it for = later, or reject it. Sounds like a whole lot more trouble than it's worth - I see no benefit to = doing any of this. Much simpler just to size your server to the maximum l= oad you want to handle. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MA= TERIAL and is thus for use only by the intended recipient. If you received = this in error, please contact the sender and delete the e-mail and its atta= chments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org