Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 83672 invoked from network); 15 May 2008 04:50:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 May 2008 04:50:20 -0000 Received: (qmail 34690 invoked by uid 500); 15 May 2008 04:50:08 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 34658 invoked by uid 500); 15 May 2008 04:50:08 -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 34647 invoked by uid 99); 15 May 2008 04:50:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 May 2008 21:50:07 -0700 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.61.61.105] (HELO usea-naimss3.unisys.com) (192.61.61.105) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 May 2008 04:49:10 +0000 Received: from usea-nagw2.na.uis.unisys.com ([129.224.72.18]) by usea-naimss3 with InterScan Message Security Suite; Wed, 14 May 2008 23:54:32 -0500 Received: from usea-nagw2.na.uis.unisys.com ([129.224.72.53]) by usea-nagw2.na.uis.unisys.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 14 May 2008 23:49:29 -0500 Received: from USEA-EXCH2.na.uis.unisys.com ([129.224.72.37]) by usea-nagw2.na.uis.unisys.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 14 May 2008 23:49:29 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Current thread count monitoring Date: Wed, 14 May 2008 23:49:25 -0500 Message-ID: <2828B04F0113CD468E6D1D51DF4362A4062800FF@USEA-EXCH2.na.uis.unisys.com> In-Reply-To: <482BBDBE.3080004@heraldlogic.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Current thread count monitoring Thread-Index: Aci2RD9mH6HDLNQ4R7+CWC2F+t/GQgAATIIg References: <482AD07C.5050204@heraldlogic.com> <000c01c8b5ff$c830fa00$0300000a@animal> <482BBDBE.3080004@heraldlogic.com> From: "Caldarale, Charles R" To: "Tomcat Users List" X-OriginalArrivalTime: 15 May 2008 04:49:29.0525 (UTC) FILETIME=[0F462E50:01C8B647] X-Virus-Checked: Checked by ClamAV on apache.org > From: Amit Bhargava [mailto:amit.bhargava@heraldlogic.com]=20 > Subject: Re: Current thread count monitoring >=20 > My understanding is that 'maxThreads' determines how many=20 > threads will be created by the Connector to deal with=20 > requests. That's the maximum number of threads for the ; if there are fewer active requests than that, there will be fewer threads in the pool. > After this, 'acceptCount' determines the number of threads=20 > which will be allowed to wait in queue. No, it's the number of *requests* that wait in the queue, until one or more threads become available to process them. > So is the current queue length that I am looking for =20 > CurrentThreadCount - maxThreads? No. I don't believe there's a means of determining the number of requests in the queue since the waiting requests are sitting in the TCP/IP stack, not in Tomcat (I think - I haven't looked at that area of the code, and it may vary depending on the connector class). - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL 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 attachments from all computers. --------------------------------------------------------------------- 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