Return-Path: <users-return-260346-archive-asf-public=cust-asf.ponee.io@tomcat.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 2AF80200C00
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Wed, 18 Jan 2017 16:28:30 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 299D8160B3A; Wed, 18 Jan 2017 15:28:30 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 73593160B34
	for <archive-asf-public@cust-asf.ponee.io>; Wed, 18 Jan 2017 16:28:29 +0100 (CET)
Received: (qmail 89507 invoked by uid 500); 18 Jan 2017 15:28:28 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 89496 invoked by uid 99); 18 Jan 2017 15:28:27 -0000
Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jan 2017 15:28:27 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 7AE08C190D
	for <users@tomcat.apache.org>; Wed, 18 Jan 2017 15:28:27 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 1.8
X-Spam-Level: *
X-Spam-Status: No, score=1.8 tagged_above=-999 required=6.31
	tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1,
	SPF_HELO_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled
Received: from mx1-lw-eu.apache.org ([10.40.0.8])
	by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)
	with ESMTP id 2cvcx0tdN29G for <users@tomcat.apache.org>;
	Wed, 18 Jan 2017 15:28:25 +0000 (UTC)
Received: from mailbox.servedge.com (72.103.82.208.static.ipv4.dnsptr.net [208.82.103.72])
	by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 346205F4AC
	for <users@tomcat.apache.org>; Wed, 18 Jan 2017 15:28:24 +0000 (UTC)
Received: (qmail 25726 invoked by uid 513); 18 Jan 2017 09:28:22 -0600
Received: from pool-74-96-79-133.washdc.fios.verizon.net (HELO Christophers-iMac.local) (chris@christopherschultz.net@74.96.79.133)
  by mailbox.servedge.com with AES128-SHA encrypted SMTP; 18 Jan 2017 09:28:22 -0600
Subject: Re: FW: tomcat 8080 thread not reduced
To: Tomcat Users List <users@tomcat.apache.org>
References: <07fc01d26b27$f2d07510$d8715f30$@zoom.us>
 <069a01d26d78$6bf3ab40$43db01c0$@zoom.us> <5878AEF8.7070006@ice-sa.com>
 <076901d26e2f$b7f487a0$27dd96e0$@zoom.us>
 <fd947d7f-383d-3202-e340-27c2ddfbf70c@christopherschultz.net>
 <020401d27060$3559e1e0$a00da5a0$@zoom.us>
 <671f9bf6-53b2-9be6-d43e-b56707e8f725@christopherschultz.net>
 <0a3e01d2714e$66eb9a70$34c2cf50$@zoom.us>
From: Christopher Schultz <chris@christopherschultz.net>
Message-ID: <47b9708c-4377-02d7-59f5-1eca56bf7046@christopherschultz.net>
Date: Wed, 18 Jan 2017 10:28:22 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0)
 Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <0a3e01d2714e$66eb9a70$34c2cf50$@zoom.us>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 18 Jan 2017 15:28:30 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Smith,

On 1/18/17 12:47 AM, smith wrote:
> So the tomcat default executor will not reduce the thread count 
> until it reach to the max configuration?

By default, you get a thread pool that isn't as smart as an executor.

> Will it reduce when it reach to max?

Not unless you use an <Executor>.

> And why the default not reduce the thread?

Because it didn't do so in the past, before <Executor> was introduced.

I'm curious: if you are willing to have e.g. 200 threads available at
any time during the life of the JVM, why does it matter if those
threads are reduced during times of inactivity?

I think of threads as a resource like memory, where if you are going
to allocate X resources, you may as well allocate X resources and be
done with it. Growing and shrinking pools of things just adds
complexity and reduces performance.

Idle threads are "free" other than using a little bit of memory. So
why is it so important for those threads to stop when they don't have
any work for a while?

- -chris

> -----Original Message----- From: Christopher Schultz
> [mailto:chris@christopherschultz.net] Sent: Tuesday, January 17,
> 2017 7:18 PM To: Tomcat Users List Subject: Re: FW: tomcat 8080
> thread not reduced
> 
> Smith,
> 
> On 1/16/17 8:22 PM, smith wrote:
>> Yes, I think thread count should be reduced when those threads
>> are idle
> 
>> Is this right? Or it will not reduced?
> 
> Id you want Tomcat to reduce the number of idle threads, you'll
> need to explicitly configure an <Executor> and use that with your
> <Connector> .
> 
> -chris
> 
>> -----Original Message----- From: Christopher Schultz 
>> [mailto:chris@christopherschultz.net] Sent: Monday, January 16, 
>> 2017 2:20 PM To: Tomcat Users List Subject: Re: FW: tomcat 8080
>> thread not reduced
> 
>> Smith,
> 
>> There are your only active <Connector>s:
> 
>> On 1/14/17 1:30 AM, smith wrote:
>>> <Connector port="8080" protocol="HTTP/1.1" maxThreads="300" 
>>> connectionTimeout="20000" redirectPort="8443" />
> 
>>> [snip]
> 
>>> <Connector port="8009" protocol="AJP/1.3" redirectPort="8443"
>>> />
> 
>> You have not changed any settings from the default. What makes
>> you think that your thread count should be reduced when those
>> threads are idle?
> 
>> -chris
> 
>> ---------------------------------------------------------------------
>
>> 
> 
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 
> 
>> ---------------------------------------------------------------------
>
>> 
> 
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 
> ---------------------------------------------------------------------
>
> 
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 
> 
> ---------------------------------------------------------------------
>
> 
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJYf4mVAAoJEBzwKT+lPKRYE1cQALnUh2se9iXDJB3r/1TiHfiy
RCEnqgjeYKaVyO0wBvG5PqyXGwedsh2i2TzuUW5zHXEi5qZhr91oZ/sEG8yOpdfv
zOb9ZeFpWJpkVuj/pa2kjszEs+gpUhth4+45ou7N9WAAkDsl4oWpHzC2aEWbNByf
u9gkt8yq5ZSccFP7/Xb7GhcjIKYpK+qK/1/U+vD9eC6sFuzpewC7+aZ1FwpQ7/6L
DlbqGRM3Uj0Yvft6YNfrmN5SY8VY4shv0f/b83tmaH8Bz2bgGhhqddAm/vSpDu44
67YU55m36NL9hTbiS4E/CnLCnZxsY7+RtR4Xz2g51KN7+OoKZIgQN7XzHYhQbTZS
NPZG1ejkE6s0R8oIjYHAO8cucSGshD7de42mdq6wrrxDrSodm29zUWS8TEgOkUBp
kuX7MzpmZt0s5YjSjwMLWXpWlmrVvbxawGNgZCFmz/At9FPt+BboymzsWQSEA+wQ
QgJHjXzp5iSskYxYdIPFCb+nhAk0AAqWG4NQs0KMRsGTqnwYYnCVT/YF2Se2kTpv
eUqlwI2rjPXiW2tKuDm+ZMENu6EbySSyngq7Ad0paIq4qXXp0QcGCN9SWSRgt6/g
YePmBR37SLKOrrkfWPFS/NRLEZg/pWhEcKVMuCDJSF/kGOca4AytQsJiZ66k0ecM
Jklop2vxVLIm1rEdO/m2
=ks8D
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org