Re: JMX currentThreadsBusy less than connections/requests when use APR connector

[linbo liao]

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 actually do 2 things at once. Perhaps
> you need more load-generating computers.
>
> > 2、Can I use currentThreadsBusy to monitor the performance of Tomcat
> > using APR connector?
>
> Yes, you can use that with any connector. The threads are Java
> threads. Only the underlying file descriptors are being managed by APR
> versus Java's BIO/NIO/2 stream managers.
>
> - -chris
>
> > 2017-03-10 0:42 GMT+08:00 Christopher Schultz
> >  :
> >
> > 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"
>  enableLookups="false" disableUploadTimeout="true"
>  connectionTimeout="2" />
> 
>  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/
> >
> > I've never used wrk. How many CPU cores does your load-generating
> > computer have?
> >
>  For APR connector, will it get one thread from the poll to
>  deal with each request?
> >
> > For both NIO/2 and APR, you'll have one accepter thread (4 in your
> > case) and one poller thread for many (400 in your case)
> > request-processing threads.
> >
> > It's possible that your server is handling the requests fast
> > enough that they never pile-up enough to use more than 40 threads.
> >
> > Congratulations: you can handle the load you are putting on the
> > server. :)
> >
> > -chris
> >
>  2017-03-08 22:45 GMT+08:00 Christopher Schultz
>   > :
> 
>  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 ab
> >>> command, find JMX currentThreadsBusy < 10 all of the
> >>> time.
> >>>
> >>> ab -n 10 -c 100 10.211.55.4:8080/
> 
> >>>
> >>> I tried to search the reason but without the result.
> >>> For BIO each thread to handle one connection, so
> >>> currentThreadsBusy can show the performance of tomcat.
> >>>
> >>> But for APR connector, what's the meaning of
> >>> currentThreadsBusy?
> 
>  Please post your  configuration.
> 
>  It seems that ab isn't a very good load-generator for
>  several reasons. But you should be able to get more than Java
>  10 threads working at a tim e.
> 
>  You are probably expecting ~100 threads busy at all times,
>  right?
> 
>  -chris
> >
> > --
> - ---
> >
> >
> >
> >
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail:
> > users-h...@tomcat.apache.org
> >
> >
> 
> >>
> >> -
> >>
> >>
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> >> For additional commands, e-mail: users-h...@tomcat.apache.org
> >>
> >>
> >
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJYwuuvAAoJEBzwKT+lPKRYfCUP/1OEAoFvKMAY2Rmh9X0Gy+WN
> ZIfnZOOUnC3onnEpgCGxucxXzfkf9jGljhIIqr+mXYu1urbhpgUaoGXT8CS7S4bn
> SSE7GSQwaQ0dyqdzhc4F2/4LzMZ1J1u+Jakn/uQhlDv4eIrYMo4tNVGEaGdVA7jo
> hU6Auy4ATY5NW/0zeefnukq8fp+CyyMGPESJGsCDL5czVjZ8zXyHo/4Px2kGyryt
> 7GM/R+8RpapnrA3WFQs65MTMn7cQAbAZOSgvzUfCC6VQicn/rMuND07OgN7I4MUG
> soEpRDjwY/41ynEUL5wID6uHsWJ9KrRldybhSQzwpI3FVNPHDCe3hRxNWPN0eULT
> /u8fCK2jyswscRqfTuk1NKEQGJ4XQqMVo+Y0cJ9BAncUPA5OUN2zD/DLnIa06yLv
> OXs3HjyFgwwEN9wMBxQyMedam5BkcjzjD6A5zdIV0isHyROa3idVl3B8HYyslhk5
> seLlCPOehr2MJsluzZjiciv4estnUf2Dm43aTc8c/1I12AMmLudAxkbGB5a4bkUt
> mb4LXpV+pPuQ/rdWrBAuyvfAXYvlgjKmcWrKltrpzFuTU+VLW8GC/1IsLwYlDcpW
> oilPZtfKEUp1hnsT8bKC1pywT3lX5MYT4acxbXcOAw1cSY+ocwPmum4J3NKBfcQP
> mR5U4hKAZ926OQYwC/f6
> =E3ng
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: JMX currentThreadsBusy less than connections/requests when use APR connector

[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 actually do 2 things at once. Perhaps
you need more load-generating computers.

> 2、Can I use currentThreadsBusy to monitor the performance of Tomcat
> using APR connector?

Yes, you can use that with any connector. The threads are Java
threads. Only the underlying file descriptors are being managed by APR
versus Java's BIO/NIO/2 stream managers.

- -chris

> 2017-03-10 0:42 GMT+08:00 Christopher Schultz
>  :
> 
> 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"
 enableLookups="false" disableUploadTimeout="true"
 connectionTimeout="2" />
 
 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/
> 
> I've never used wrk. How many CPU cores does your load-generating 
> computer have?
> 
 For APR connector, will it get one thread from the poll to
 deal with each request?
> 
> For both NIO/2 and APR, you'll have one accepter thread (4 in your 
> case) and one poller thread for many (400 in your case) 
> request-processing threads.
> 
> It's possible that your server is handling the requests fast
> enough that they never pile-up enough to use more than 40 threads.
> 
> Congratulations: you can handle the load you are putting on the
> server. :)
> 
> -chris
> 
 2017-03-08 22:45 GMT+08:00 Christopher Schultz 
  :
 
 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 ab
>>> command, find JMX currentThreadsBusy < 10 all of the
>>> time.
>>> 
>>> ab -n 10 -c 100 10.211.55.4:8080/
 
>>> 
>>> I tried to search the reason but without the result.
>>> For BIO each thread to handle one connection, so
>>> currentThreadsBusy can show the performance of tomcat.
>>> 
>>> But for APR connector, what's the meaning of 
>>> currentThreadsBusy?
 
 Please post your  configuration.
 
 It seems that ab isn't a very good load-generator for
 several reasons. But you should be able to get more than Java
 10 threads working at a tim e.
 
 You are probably expecting ~100 threads busy at all times,
 right?
 
 -chris
> 
> --
- ---
>
>
>
> 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail:
> users-h...@tomcat.apache.org
> 
> 
 
>> 
>> -
>>
>> 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>> 
>> 
> 
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJYwuuvAAoJEBzwKT+lPKRYfCUP/1OEAoFvKMAY2Rmh9X0Gy+WN
ZIfnZOOUnC3onnEpgCGxucxXzfkf9jGljhIIqr+mXYu1urbhpgUaoGXT8CS7S4bn
SSE7GSQwaQ0dyqdzhc4F2/4LzMZ1J1u+Jakn/uQhlDv4eIrYMo4tNVGEaGdVA7jo
hU6Auy4ATY5NW/0zeefnukq8fp+CyyMGPESJGsCDL5czVjZ8zXyHo/4Px2kGyryt
7GM/R+8RpapnrA3WFQs65MTMn7cQAbAZOSgvzUfCC6VQicn/rMuND07OgN7I4MUG
soEpRDjwY/41ynEUL5wID6uHsWJ9KrRldybhSQzwpI3FVNPHDCe3hRxNWPN0eULT
/u8fCK2jyswscRqfTuk1NKEQGJ4XQqMVo+Y0cJ9BAncUPA5OUN2zD/DLnIa06yLv
OXs3HjyFgwwEN9wMBxQyMedam5BkcjzjD6A5zdIV0isHyROa3idVl3B8HYyslhk5
seLlCPOehr2MJsluzZjiciv4estnUf2Dm43aTc8c/1I12AMmLudAxkbGB5a4bkUt
mb4LXpV+pPuQ/rdWrBAuyvfAXYvlgjKmcWrKltrpzFuTU+VLW8GC/1IsLwYlDcpW
oilPZtfKEUp1hnsT8bKC1pywT3lX5MYT4acxbXcOAw1cSY+ocwPmum4J3NKBfcQP
mR5U4hKAZ926OQYwC/f6
=E3ng
-END PGP SIGNATURE-

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

Re: JMX currentThreadsBusy less than connections/requests when use APR connector

[linbo liao]

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 Connector configuration:
> >
> >  > protocol="org.apache.coyote.http11.Http11AprProtocol"
> > maxHttpHeaderSize="8192" maxThreads="400" acceptorThreadCount="4"
> > maxKeepAliveRequests="-1" enableLookups="false"
> > disableUploadTimeout="true" connectionTimeout="2" />
> >
> > 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/
>
> I've never used wrk. How many CPU cores does your load-generating
> computer have?
>
> > For APR connector, will it get one thread from the poll to deal
> > with each request?
>
> For both NIO/2 and APR, you'll have one accepter thread (4 in your
> case) and one poller thread for many (400 in your case)
> request-processing threads.
>
> It's possible that your server is handling the requests fast enough
> that they never pile-up enough to use more than 40 threads.
>
> Congratulations: you can handle the load you are putting on the server.
> :)
>
> - -chris
>
> > 2017-03-08 22:45 GMT+08:00 Christopher Schultz
> >  >> :
> >
> > 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 ab command,
>  find JMX currentThreadsBusy < 10 all of the time.
> 
>  ab -n 10 -c 100 10.211.55.4:8080/
> >
> 
>  I tried to search the reason but without the result. For BIO
>  each thread to handle one connection, so currentThreadsBusy
>  can show the performance of tomcat.
> 
>  But for APR connector, what's the meaning of
>  currentThreadsBusy?
> >
> > Please post your  configuration.
> >
> > It seems that ab isn't a very good load-generator for several
> > reasons. But you should be able to get more than Java 10 threads
> > working at a tim e.
> >
> > You are probably expecting ~100 threads busy at all times, right?
> >
> > -chris
> >>
> >> -
> >>
> >>
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> >> For additional commands, e-mail: users-h...@tomcat.apache.org
> >>
> >>
> >
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJYwYX2AAoJEBzwKT+lPKRYi2EP/1krL32JxAAkVa1C+lZiehoC
> KCufHoT/t4YK8yZRth+3TXK7wSqINwuZf+6PQXlQaR+Vy6chacS+DGvebsvBj58S
> q8Piu6kcTlnuK21nBBTW6pQ6vvLA7TpEaup8eCB3lVWIuUoTQlAL+OerAYP6M7pk
> 8oVHMatIJLSzhdjWo1S7Hz90TonGZvPb9Mk5587Dp8G2dKTu78abMVbGiR7xOn7g
> FMWS/k/HbAnGbkfwdTHww/inrXxfODfhcRuyyQW/j46PP6mQbzcjdjLuUGsKy6cm
> 8yUuy0h88o4l95X8oDf3yaI5nWZXvYuIHvT/9+L9DVhzpllol9CzBY6vXSFyuvQD
> Sd9GCNNgvQjN4CoKvlBeUIk7LOF7p4a15bBfDFnEAJVB7HGzU/Rx8Fp1+ON57pLA
> gN+IBT7joqCWissmZyO/lsQ6erQR2jmFvHBodXOEYFIy3WF3zGgt4K8KPfSxSCXu
> HtEuTR0enxBzSgfq0sx2nZxoetNn41BKPQo+T9E8zHTghoVGXHK8bpf1Z3/NZ2IP
> /9FUix6rxj+y1RaeQqXZmfnHPwRDsl+RV0tO/nGyqiD4LB9Gb+bM7yNZxsSTs3Uk
> YT6ZoZ1Dzys9Lifv+tFXK4pOWfeNAYo/3b58zGhHAlyEQySza8DgxTtsTql4i7TF
> Ebqjos00OCr3EeLg5ODi
> =6IxB
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: JMX currentThreadsBusy less than connections/requests when use APR connector

[Christopher Schultz]

-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" enableLookups="false"
> disableUploadTimeout="true" connectionTimeout="2" />
> 
> 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/

I've never used wrk. How many CPU cores does your load-generating
computer have?

> For APR connector, will it get one thread from the poll to deal
> with each request?

For both NIO/2 and APR, you'll have one accepter thread (4 in your
case) and one poller thread for many (400 in your case)
request-processing threads.

It's possible that your server is handling the requests fast enough
that they never pile-up enough to use more than 40 threads.

Congratulations: you can handle the load you are putting on the server.
:)

- -chris

> 2017-03-08 22:45 GMT+08:00 Christopher Schultz
> > :
> 
> 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 ab command,
 find JMX currentThreadsBusy < 10 all of the time.
 
 ab -n 10 -c 100 10.211.55.4:8080/
> 
 
 I tried to search the reason but without the result. For BIO
 each thread to handle one connection, so currentThreadsBusy
 can show the performance of tomcat.
 
 But for APR connector, what's the meaning of
 currentThreadsBusy?
> 
> Please post your  configuration.
> 
> It seems that ab isn't a very good load-generator for several
> reasons. But you should be able to get more than Java 10 threads
> working at a tim e.
> 
> You are probably expecting ~100 threads busy at all times, right?
> 
> -chris
>> 
>> -
>>
>> 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>> 
>> 
> 
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJYwYX2AAoJEBzwKT+lPKRYi2EP/1krL32JxAAkVa1C+lZiehoC
KCufHoT/t4YK8yZRth+3TXK7wSqINwuZf+6PQXlQaR+Vy6chacS+DGvebsvBj58S
q8Piu6kcTlnuK21nBBTW6pQ6vvLA7TpEaup8eCB3lVWIuUoTQlAL+OerAYP6M7pk
8oVHMatIJLSzhdjWo1S7Hz90TonGZvPb9Mk5587Dp8G2dKTu78abMVbGiR7xOn7g
FMWS/k/HbAnGbkfwdTHww/inrXxfODfhcRuyyQW/j46PP6mQbzcjdjLuUGsKy6cm
8yUuy0h88o4l95X8oDf3yaI5nWZXvYuIHvT/9+L9DVhzpllol9CzBY6vXSFyuvQD
Sd9GCNNgvQjN4CoKvlBeUIk7LOF7p4a15bBfDFnEAJVB7HGzU/Rx8Fp1+ON57pLA
gN+IBT7joqCWissmZyO/lsQ6erQR2jmFvHBodXOEYFIy3WF3zGgt4K8KPfSxSCXu
HtEuTR0enxBzSgfq0sx2nZxoetNn41BKPQo+T9E8zHTghoVGXHK8bpf1Z3/NZ2IP
/9FUix6rxj+y1RaeQqXZmfnHPwRDsl+RV0tO/nGyqiD4LB9Gb+bM7yNZxsSTs3Uk
YT6ZoZ1Dzys9Lifv+tFXK4pOWfeNAYo/3b58zGhHAlyEQySza8DgxTtsTql4i7TF
Ebqjos00OCr3EeLg5ODi
=6IxB
-END PGP SIGNATURE-

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

Re: JMX currentThreadsBusy less than connections/requests when use APR connector

[linbo liao]

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-03-08 22:45 GMT+08:00 Christopher Schultz :

> -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 ab command, find
> > JMX currentThreadsBusy < 10 all of the time.
> >
> > ab -n 10 -c 100 10.211.55.4:8080/
> >>
> >
> > I tried to search the reason but without the result. For BIO each
> > thread to handle one connection, so currentThreadsBusy can show the
> > performance of tomcat.
> >
> > But for APR connector, what's the meaning of currentThreadsBusy?
>
> Please post your  configuration.
>
> It seems that ab isn't a very good load-generator for several reasons.
> But you should be able to get more than Java 10 threads working at a tim
> e.
>
> You are probably expecting ~100 threads busy at all times, right?
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJYwBkcAAoJEBzwKT+lPKRYxLQQAJsr6IWI6kRaCmEg+SMZRKco
> 8ALINQrUvkUZYvIx23wlr7cKpmZ0g02RVXKn8+usEsiZ9vBwb6ap3HV7RCM/xl33
> zaAuxYPNsJ9bMUnTTkxr5ciSvMGI1FhvTWazEHprLoiPV1RtBwKBLTbztxQTQfO4
> 0AqfRgucC0NJbEPzVwKc6FB9qUl+U3XROUCC2AKmaFIHbQDSPnCLKX3hyzaOsH7R
> cd8nr3teQxoisIT3MuhaWPMDdfdKbe0ZmPj39borGUvHwUL1kRCz3wYvoQN3kCg5
> YHxjV3B9TYqU1q0TiILuQvO1rbG8G3QLIXFz8eNdX1XwS0oIRYAJfhTqSbxBuTlm
> 1jSrS716Kd2JkmNWmoSLHFSvBUkevirh5ZL6B9SuFvV449lCgBjwV//wiE/oskbT
> 6+jKDrL0ReCw8NtfWbCaeXmltyR9ir7x4SSjT1iSpg/ZGnxmKkdiZFoR/mWDcH5G
> y4TwbmDC0RNAfC9lNCp5cBtrIZkoJM53iOtUCB22I3tco/hNB91TV8WN5RKqAHl1
> Cn7FLfSGwBQRv3UHfeWmMwxcP4Q4FxMbpqtHv2PAcjB7skcsbR6BUth9gY3FbWmF
> DvKL941SuDPLtA9IVr/nplvwlMUV/QQNi+tZXuL9Xf1GoCgcM7uVQkcuhlf+QpFm
> ELHZ5kXO3Zs7RrycRnL3
> =6bmJ
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: JMX currentThreadsBusy less than connections/requests when use APR connector

[Christopher Schultz]

-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 ab command, find
> JMX currentThreadsBusy < 10 all of the time.
> 
> ab -n 10 -c 100 10.211.55.4:8080/
>> 
> 
> I tried to search the reason but without the result. For BIO each
> thread to handle one connection, so currentThreadsBusy can show the
> performance of tomcat.
> 
> But for APR connector, what's the meaning of currentThreadsBusy?

Please post your  configuration.

It seems that ab isn't a very good load-generator for several reasons.
But you should be able to get more than Java 10 threads working at a tim
e.

You are probably expecting ~100 threads busy at all times, right?

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJYwBkcAAoJEBzwKT+lPKRYxLQQAJsr6IWI6kRaCmEg+SMZRKco
8ALINQrUvkUZYvIx23wlr7cKpmZ0g02RVXKn8+usEsiZ9vBwb6ap3HV7RCM/xl33
zaAuxYPNsJ9bMUnTTkxr5ciSvMGI1FhvTWazEHprLoiPV1RtBwKBLTbztxQTQfO4
0AqfRgucC0NJbEPzVwKc6FB9qUl+U3XROUCC2AKmaFIHbQDSPnCLKX3hyzaOsH7R
cd8nr3teQxoisIT3MuhaWPMDdfdKbe0ZmPj39borGUvHwUL1kRCz3wYvoQN3kCg5
YHxjV3B9TYqU1q0TiILuQvO1rbG8G3QLIXFz8eNdX1XwS0oIRYAJfhTqSbxBuTlm
1jSrS716Kd2JkmNWmoSLHFSvBUkevirh5ZL6B9SuFvV449lCgBjwV//wiE/oskbT
6+jKDrL0ReCw8NtfWbCaeXmltyR9ir7x4SSjT1iSpg/ZGnxmKkdiZFoR/mWDcH5G
y4TwbmDC0RNAfC9lNCp5cBtrIZkoJM53iOtUCB22I3tco/hNB91TV8WN5RKqAHl1
Cn7FLfSGwBQRv3UHfeWmMwxcP4Q4FxMbpqtHv2PAcjB7skcsbR6BUth9gY3FbWmF
DvKL941SuDPLtA9IVr/nplvwlMUV/QQNi+tZXuL9Xf1GoCgcM7uVQkcuhlf+QpFm
ELHZ5kXO3Zs7RrycRnL3
=6bmJ
-END PGP SIGNATURE-

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

RE: JMX currentThreadsBusy less than connections/requests when use APR connector

[smith]

Our production usage also has same phenomenon that my "currentThreadsBusy" 
always not high (3-5), but my "currentThreadCount" will go to 200-300 
sometimes. I know that at some busy time, more threads will be created, so the 
thread pool get high, but at the same time, the busy 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 APR 
connector

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.

"currentThreadCount" is current threads in thread pool. To track thread pool 
usage, you can use this counter.

Thanks!
Suvendu

On Wed, Mar 8, 2017 at 8:44 AM, linbo liao <llbg...@gmail.com> wrote:
> 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 tried to search the reason but without the result. For BIO each 
> thread to handle one connection, so currentThreadsBusy can show the 
> performance of tomcat.
>
> But for APR connector, what's the meaning of currentThreadsBusy?
>
> Thanks in advance.
>
> Thanks,
> Linbo

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



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

Re: JMX currentThreadsBusy less than connections/requests when use APR connector

[Suvendu Sekhar Mondal]

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.

"currentThreadCount" is current threads in thread pool. To track
thread pool usage, you can use this counter.

Thanks!
Suvendu

On Wed, Mar 8, 2017 at 8:44 AM, linbo liao  wrote:
> 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 tried to search the reason but without the result. For BIO each thread to
> handle one connection, so currentThreadsBusy can show the performance of
> tomcat.
>
> But for APR connector, what's the meaning of currentThreadsBusy?
>
> Thanks in advance.
>
> Thanks,
> Linbo

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