tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pid <...@pidster.com>
Subject Re: 答复: Re:Tomcat7.0-Setting property 'threadPriority' did not find a matching property
Date Mon, 03 Dec 2012 15:56:54 GMT
On 03/12/2012 15:31, Christopher Schultz wrote:
> Pid,
> 
> On 12/3/12 3:35 AM, Pid * wrote:
>> On 3 Dec 2012, at 05:43, Weixiang <kurt.weixiang@huawei.com>
>> wrote:
> 
>>> Thank you, after I changed 'java.lang.Thread#MAX_PRIORITY' to
>>> integer '10', the warning disappeared in tomcat 7.
>>>
>>> But I user 'java.lang.Thread#MAX_PRIORITY' in tomcat 6.0.35 and
>>> there's no any warning.
>>>
>>> So I was wondering whether the tomcat 6 block this warning or
>>> not?
> 
>> I'd be interested to hear about the load profile and application 
>> behaviour you are attempting to modify (improve?).
> 
> If you increase the thread priority, the threads will run faster. Duh.

Quite.  Alternatively, it might be the case that setting the thread
priority will have no measurable effect at all.  If any effect.


The OP is trying to set the thread priority on what appears to be an
HTTP connector (marked in a comment for 'management').

Of the 3 connectors configured, the config is as follows:

 port   protocol   threads  accept
 13089  BIO+HTTP   120      200
 13080  NIO+HTTP   1200     2000
 13443  NIO+HTTPS  200      2000

The value of the acceptCount attributes are bonkers, IMHO.  This should
never be larger than the number of threads in the pool - if the apps
really need to support >1200 inbounds, either increase the number of
threads or add another Tomcat instance.

The HTTPS thread count value (being the default) *may* be
accurate/appropriate or it might not, but it seems low given the other
numbers.


p


-- 

[key:62590808]


Mime
View raw message