ion is in
the keepalive state, but it's not consuming a thread.
- -chris
> -Original Message- From: Christopher Schultz
> [mailto:ch...@christopherschultz.net] Sent: Friday, January 20,
> 2017 10:29 PM To: Tomcat Users List Subject: Re: FW: tomcat 8080
> thread not reduced
>
&
hultz
[mailto:ch...@christopherschultz.net] Sent: Thursday, January 19,
2017 4:38 PM To: Tomcat Users List Subject: Re: FW: tomcat 8080 thread
not reduced
Smith,
On 1/18/17 8:25 PM, smith wrote:
I don't care if the threads will be reduced, I just want to know why.
Okay.
And we want to use the ac
Schultz [mailto:ch...@christopherschultz.net]
Sent: Friday, January 20, 2017 10:29 PM
To: Tomcat Users List
Subject: Re: FW: tomcat 8080 thread not reduced
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Smith,
On 1/19/17 9:59 PM, smith wrote:
>> "busy" is the same as "activ
z
> [mailto:ch...@christopherschultz.net] Sent: Thursday, January 19,
> 2017 4:38 PM To: Tomcat Users List Subject: Re: FW: tomcat 8080
> thread not reduced
>
> Smith,
>
> On 1/18/17 8:25 PM, smith wrote:
>> I don't care if the threads will be reduced, I just want to know
[mailto:ch...@christopherschultz.net]
Sent: Thursday, January 19, 2017 4:38 PM
To: Tomcat Users List
Subject: Re: FW: tomcat 8080 thread not reduced
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Smith,
On 1/18/17 8:25 PM, smith wrote:
I don't care if the threads will be reduced, I j
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Thursday, January 19, 2017 4:38 PM
To: Tomcat Users List
Subject: Re: FW: tomcat 8080 thread not reduced
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Smith,
On 1/18/17 8:25 PM, smith wrote:
> I
ads if necessary)
2. Shared thread-pools (no need to have port 8080 and 8443 with
separate pools)
- -chris
> -Original Message- From: Christopher Schultz
> [mailto:ch...@christopherschultz.net] Sent: Wednesday, January 18,
> 2017 3:28 PM To: Tomcat Users List Subject: Re: FW: tomc
To: Tomcat Users List
Subject: Re: FW: tomcat 8080 thread not reduced
-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, y
7 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?
>
&g
te will be ignored.
>>>
>>> So in fact the only thing wrong, is the online documentation
>>> for the Connectors : the minSpareThreads attribute should be
>>> removed (since it is anyway ignored). That seems to have been
>>> an oversight ever since t
onfiguring an Executor.
You need to configure the itself, and then in your , refer to that
Executor).
-Original Message-
From: André Warnier (tomcat) [mailto:a...@ice-sa.com]
Sent: Wednesday, January 18, 2017 9:41 AM
To: users@tomcat.apache.org
Subject: Re: FW: tomcat 8080 thread n
) [mailto:a...@ice-sa.com]
Sent: Wednesday, January 18, 2017 9:41 AM
To: users@tomcat.apache.org
Subject: Re: FW: tomcat 8080 thread not reduced
Hi.
I believe that what Philippe mentions below is somewhat different : in his
configuration, there is apparently a front-end httpd server, which communicates
os to get tomcat manager result, not high than
> 10). This is strange
>
> -Original Message-
> From: Philippe Busque [mailto:pbus...@mediagrif.com]
> Sent: Monday, January 16, 2017 8:09 PM
> To: users@tomcat.apache.org
> Subject: Re: Re: FW: tomcat 8080 thread not reduced
>
result, not high than 10). This
is strange
-Original Message-
From: Philippe Busque [mailto:pbus...@mediagrif.com]
Sent: Monday, January 16, 2017 8:09 PM
To: users@tomcat.apache.org
Subject: Re: Re: FW: tomcat 8080 thread not reduced
We're having a similar issues with our n
, 2017 8:09 PM
To: users@tomcat.apache.org
Subject: Re: Re: FW: tomcat 8080 thread not reduced
We're having a similar issues with our numberous Tomcat instances.
Our connector config look like this.
Sometime, the number of active connection would jump very high (up to 190), due
to some
]
Sent: Tuesday, January 17, 2017 7:18 PM
To: Tomcat Users List
Subject: Re: FW: tomcat 8080 thread not reduced
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Smith,
On 1/16/17 8:22 PM, smith wrote:
> Yes, I think thread count should be reduced when those threads are
> idle
>
> I
o explicitly configure an and use that with your
.
- -chris
> -Original Message- From: Christopher Schultz
> [mailto:ch...@christopherschultz.net] Sent: Monday, January 16,
> 2017 2:20 PM To: Tomcat Users List Subject: Re: FW: tomcat 8080
> thread not reduced
>
> Smith,
>
Yes, I also think it should act like this, but it did not.
-Original Message-
From: André Warnier (tomcat) [mailto:a...@ice-sa.com]
Sent: Monday, January 16, 2017 2:33 PM
To: users@tomcat.apache.org
Subject: Re: FW: tomcat 8080 thread not reduced
On 16.01.2017 15:19, Christopher Schultz
Yes, I think thread count should be reduced when those threads are idle
Is this right? Or it will not reduced?
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, January 16, 2017 2:20 PM
To: Tomcat Users List
Subject: Re: FW: tomcat 8080
: Monday, January 16, 2017 10:08 AM
To: users@tomcat.apache.org
Subject: Re: FW: tomcat 8080 thread not reduced
On 16.01.2017 09:50, smith wrote:
Busy one is process customer request, do not know what non-busy one is
doing, always keep 120 for many days. I don't think 20s timeout will
not cause so
On 16.01.2017 15:19, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Smith,
There are your only active s:
On 1/14/17 1:30 AM, smith wrote:
[snip]
You have not changed any settings from the default. What makes you
think that your thread count should be reduced
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Smith,
There are your only active s:
On 1/14/17 1:30 AM, smith wrote:
> connectionTimeout="2" redirectPort="8443" />
>
> [snip]
>
>
You have not changed any settings from the default. What makes you
think that your thread count should be
: Monday, January 16, 2017 10:08 AM
To: users@tomcat.apache.org
Subject: Re: FW: tomcat 8080 thread not reduced
On 16.01.2017 09:50, smith wrote:
Busy one is process customer request, do not know what non-busy one is
doing, always keep 120 for many days. I don't think 20s timeout will
not cause so long
We has same problem on dev env that no any traffic to the serive, will try on
dev first
-Original Message-
From: André Warnier (tomcat) [mailto:a...@ice-sa.com]
Sent: Monday, January 16, 2017 10:08 AM
To: users@tomcat.apache.org
Subject: Re: FW: tomcat 8080 thread not reduced
tomcat) [mailto:a...@ice-sa.com]
Sent: Friday, January 13, 2017 10:42 AM
To: users@tomcat.apache.org
Subject: Re: FW: tomcat 8080 thread not reduced
On 13.01.2017 09:38, smith wrote:
From: smith [mailto:smith@zoom.us]
Sent: Tuesday, January 10, 2017 9:57 AM
To: 'users'
Subject: tomcat 8080 thread
AM
To: users@tomcat.apache.org
Subject: Re: FW: tomcat 8080 thread not reduced
On 16.01.2017 03:41, Smith Hua wrote:
>
> actually there is not much busy threads, less tahn 10,so i think this
> parameter may has nothing to do with this
It depends on what you call "busy". Wha
On 14.01.2017 07:30, smith wrote:
The server.xml:
-Original Message-
From: André Warnier (tomcat) [mailto:a...@ice-sa.com]
Sent: Friday, January 13, 2017 10:42 AM
-Original Message-
From: André Warnier (tomcat) [mailto:a...@ice-sa.com]
Sent: Friday, January 13, 2017 10:42 AM
To: users@tomcat.apache.org
Subject: Re: FW: tomcat 8080 thread not reduced
On 13.01.2017 09:38, smith wrote:
From: smith [mailto
-
From: André Warnier (tomcat) [mailto:a...@ice-sa.com]
Sent: Friday, January 13, 2017 10:42 AM
To: users@tomcat.apache.org
Subject: Re: FW: tomcat 8080 thread not reduced
On 13.01.2017 09:38, smith wrote:
>
>
>
>
> From: smith [mailto:smith@zoom.us]
> Sent: Tuesday, Januar
On 13.01.2017 09:38, smith wrote:
From: smith [mailto:smith@zoom.us]
Sent: Tuesday, January 10, 2017 9:57 AM
To: 'users'
Subject: tomcat 8080 thread not reduced
Hi,
We have installed Apache Tomcat/8.0.14, and found that after one period of
time, the thread count for 8080(our port
30 matches
Mail list logo
