-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
이의준,
On 3/30/18 10:51 PM, 이의준 wrote:
> Hi! Christopher Schultz. Thank you for your reply. 1.
> KeepAliveTimeout is not set but connectionTimeout = "15000", so
> keepAliveTimeout is automatically set to 15 seconds?
Yes. You might want to raise t
st regards.
-Original Message-
From: Christopher Schultz
Sent: Saturday, March 31, 2018 2:23 AM
To: users@tomcat.apache.org
Subject: Re: Is the thread status of tomcat 8.0.44 normal?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
이의준,
On 3/29/18 9:05 PM, 이의준 wrote:
> Thank you, Mr. Christ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
이의준,
On 3/29/18 9:05 PM, 이의준 wrote:
> Thank you, Mr. Christopher Schultz.
>
> If the keepalivetimeout value is the same, it is not the
> difference between tomcat7 and tomcat8 eventually, it is the Thread
> state corresponding to the inflowing requ
d.conf fragment on apache http server connected to Tomcat 8.
KeepAlive On
KeepAliveTimeout 30
MaxKeepAliveRequests 0
Timeout 60
Best regards!
-Original Message-
From: Christopher Schultz
Sent: Friday, March 30, 2018 1:15 AM
To: users@tomcat.apache.org
Subject: Re: Is the thread status of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
이의준,
On 3/28/18 8:28 PM, 이의준 wrote:
> I posted the same question a few days ago, but it was not a
> satisfactory answer.
>
> So I ask again.
>
>
>
> Test sequence and inquiry contents
>
> 1. In the local test, the same load (hp-jmeter) for tomc
On 3/28/2018 6:28 PM, 이의준 wrote:
Test sequence and inquiry contents
1. In the local test, the same load (hp-jmeter) for tomcat 7, 8 5 minutes,
2. Thread dump generated after 5 minutes of load termination
3. Most Thread in Tomcat 7 is in TIME_WAITING state (normally OK)
4. Thread in Tomcat 8 m
Hi!
I posted the same question a few days ago, but it was not a satisfactory
answer.
So I ask again.
Test sequence and inquiry contents
1. In the local test, the same load (hp-jmeter) for tomcat 7, 8 5 minutes,
2. Thread dump generated after 5 minutes of load termination
3. Most Thread
