tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: Manager connector status
Date Wed, 04 Apr 2018 17:31:27 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Mark,

On 4/4/18 9:52 AM, Mark Thomas wrote:
> On 04/04/18 14:29, Christopher Schultz wrote:
>> All,
>> 
>> I'm running 8.5.29 and I'm looking at the manager application, 
>> specifically at the Connectors list on the "Server Status" page.
>> 
>> I have two connectors:
>> 
>> 1. ajp-nio-8215
>> 
>> 2. http-nio-127.0.0.1-8217
>> 
>> The server is idle (it's my own desktop) and I loaded the Server 
>> Status page over the HTTP connector. However, both connectors say
>> that the "Current thread busy" count is "1". Why is the AJP
>> connector "using" a thread? It should be doing nothing, right?
> 
> I don't see this on a clean install.
> 
> I do see this if I configure both the AJP and HTTP connector to use
> a shared executor. In this case, the thread stats reported are for
> the executor.

Right, because none of the Connectors in the default configuration use
an Executor.

But what about the "1 thread always being used" thing?

>> Another odd thing is that the connector says the "Max Threads" is
>> -1. That may be true for the connector itself because I'm using
>> an Executor. But the executor does have a thread-limit and that's
>> not being shown.
>> 
>> The current thread count and current thread busy counts are sane 
>> values, so those must be coming from the Executor. Why not the
>> "max threads" value?
> 
> That would need some svn archaeology. From memory there have been
> some changes around this area over the years as various edge cases
> emerge.
> 
> Ah. And there you have the answer: 
> https://bz.apache.org/bugzilla/show_bug.cgi?id=60319
> 
> Because the Connector and Executor have separate attributes for 
> maxThreads, minSpareThreads and threadPriority the getters and
> setters were providing inconsistent / misleading values. Returning
> -1 was an attempt to indicate that the attribute was not being used
> and that you should look elsewhere for the value.
> 
> The dynamic stats (current thread-pool size, active threads, etc.)
> can be provided in a consistent manner so don;t need this
> treatment.

That's what I figured, but there is no information about Executors in
the manager.

Would it be better to introduce more information about Executors in
the Manager, or to change the Manager to show the Executor information
when one is in use?

I see this as a minor bug since you can't see the "max threads" for a
Connector when an Executor is in play.

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

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlrFC+4ACgkQHPApP6U8
pFi1rg//VecfQAkDqyIEMcBsbNm/F4vqnTrJ5HYj80yGI4mEtuFmA9Nz9VaVqUHa
ZKFYRd8NS1+cphLQNBrfkEQTcd+K4JYkhGgCpSapR04nXhKVc7pUiWk+C/qWbdCV
r3IrJM3EY+3IUHzQDLzige6dMpTFT4lsNKQGPSaOEFaeuHzO2wL2is067fGVf8qN
MZ2c3HKhac4TRC6Ytg4lOF+hNhhYsnVIOA5LpVtZ7rBcVBl3HPCI/Qm2VC5L5LrO
RbuRje6qCbtFtiTM0Zd9eKxPuc8ObS6NhHLeC0HJkOiCCkq361DZDBzXaMpSzqHN
nr5S9sviozbh8QfCN0IgxqYpdB6hHpUtYrxSOOTi0TUvcJEgoD0Ne5daDGSrHp2O
/ZgFCAxWRRLBsccVaeRXyCcZ8zVF47eXfIH5I52ACNh0LOHJu6rC3jlZnfa43TOO
qjobAjFlSQi6AHAc4xFK/AFvEl65rDHTBQgY3fi53SFAFOH65K7bH6fvCBRMvkuu
MYKG161ukl5GvoWWTIWMhfuQCw+elC4eYPLqclpBkwlwnaDymOwDf5uAcEHTdr/d
XjQ+6yau6G+KFV/64haRYNjB+RtGz8U+CPG6XJkpqXen2ywq/XvgA/5zLQyjNMjT
SAQCEnpn69bXUOkjRru9Q8cYiN+QlGFl6X22I7Cvx50fwOekblg=
=qni4
-----END PGP SIGNATURE-----

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


Mime
View raw message