Hi Chris,
Thank you for your help. I will monitor it via JMX.
2017-03-11 2:08 GMT+08:00 Christopher Schultz
:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Linbo,
>
> On 3/9/17 7:31 PM, linbo liao wrote:
> > 1、The load-generating vm has 2 cores.
>
> With only 2 cores, you can only act
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Linbo,
On 3/9/17 7:31 PM, linbo liao wrote:
> 1、The load-generating vm has 2 cores.
With only 2 cores, you can only actually do 2 things at once. Perhaps
you need more load-generating computers.
> 2、Can I use currentThreadsBusy to monitor the perf
1、The load-generating vm has 2 cores.
2、Can I use currentThreadsBusy to monitor the performance of Tomcat using
APR connector?
2017-03-10 0:42 GMT+08:00 Christopher Schultz
:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Linbo,
>
> On 3/8/17 8:13 PM, linbo liao wrote:
> > Here is the C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Linbo,
On 3/8/17 8:13 PM, linbo liao wrote:
> Here is the Connector configuration:
>
> protocol="org.apache.coyote.http11.Http11AprProtocol"
> maxHttpHeaderSize="8192" maxThreads="400" acceptorThreadCount="4"
> maxKeepAliveRequests="-1" enableLo
Hi,
Here is the Connector configuration:
I use wrk, the currentThreadsBusy is higher than the value in ab testing,
but most of time is less than 40.
./wrk -t100 -c 100 -d 10s http://10.211.55.4:8080/
For APR connector, will it get one thread from the poll to deal with each
request?
2017
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Linbo,
On 3/7/17 10:14 PM, linbo liao wrote:
> I setup local environment to test Tomcat monitor.
>
> The Environment:
>
> Tomcat: 8.5.5 VM: Ubuntu 14.04.1 LTS HTTP PORT: 8080 IP:
> 10.211.55.4
>
> Tomcat use APR connector, I test the tomcat via a
sy threads will also
increase, but I never catch when it also went high.
-Original Message-
From: Suvendu Sekhar Mondal [mailto:suv3...@gmail.com]
Sent: Wednesday, March 08, 2017 1:43 PM
To: Tomcat Users List
Subject: Re: JMX currentThreadsBusy less than connections/requests when use A
Linbo,
"currentThreadsBusy" is number of busy threads. These are the threads
are being actively use. If you are seeing this count > 0 for long
time(depending on your application type), then most likely you have
"hung thread". In that case thread dump analysis will show you root of
the problem.
"c
Hi,
I setup local environment to test Tomcat monitor.
The Environment:
Tomcat: 8.5.5
VM: Ubuntu 14.04.1 LTS
HTTP PORT: 8080
IP: 10.211.55.4
Tomcat use APR connector, I test the tomcat via ab command, find JMX
currentThreadsBusy < 10 all of the time.
ab -n 10 -c 100 10.211.55.4:8080/
>
I t
