Re: 答复: Re:Tomcat7.0-Setting property 'threadPriority' did not find a matching property
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 >> 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] signature.asc Description: OpenPGP digital signature
Re: 答复: Re:Tomcat7.0-Setting property 'threadPriority' did not find a matching property
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Weixiang, On 12/3/12 12:42 AM, Weixiang 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? Tomcat 6 silently ignores values it cannot set properly. In Tomcat 6, you are also *not* setting your thread priority to MAX_PRIORITY -- you just don't know it. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlC8xfwACgkQ9CaO5/Lv0PAC/QCglovQAm1bbQSHyhjSgi0VmWo7 1UsAoJAKNqCzxbmQxZhWqKkvxIf16yYx =q0Jc -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: 答复: Re:Tomcat7.0-Setting property 'threadPriority' did not find a matching property
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pid, On 12/3/12 3:35 AM, Pid * wrote: > On 3 Dec 2012, at 05:43, Weixiang > 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. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlC8xbYACgkQ9CaO5/Lv0PDZQACgnyQANWU+7/VY/JRob4sQePsw 8fsAoKMywENSuQA2GMEJ6kjkYULNIfO0 =pKNh -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: 答复: Re:Tomcat7.0-Setting property 'threadPriority' did not find a matching property
On 3 Dec 2012, at 05:43, Weixiang 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?).
p
>
> -邮件原件-
> 发件人: xueshengzj [mailto:xueshen...@163.com]
> 发送时间: 2012年12月3日 13:36
> 收件人: Tomcat Users List
> 主题: Re:Tomcat7.0-Setting property 'threadPriority' did not find a matching
> property
>
> Hi, have you seen the error that show it. It tell us that the property is not
> matched. The thread priority for threads in the executor, the default is
> Thread.NORM_PRIORITY. It should return integer.
>
>
>
>
>
>
> 在 2012-12-03 12:53:08，Weixiang 写道：
>
>
> Tomcat version：7.0.29
>
>
>
> Question：
>
> I config in my server.xml for a HTTP Connector named “MGMT”:
>
>
>
> threadPriority="java.lang.Thread#Thread.MAX_PRIORITY"
>
>
>
> When application is starting up，the catalina.out gives some warning
> information:
>
>
>
> WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property
> 'threadPriority' to 'java.lang.Thread#MAX_PRIORITY' did not find a matching
> property.
>
>
>
> I search on google and did not get any useful help;
>
>
>
> I also search documentation on the apache.org and make sure that
> 'threadPriority' is a legal attribute for HTTP Connector，so I wonder why
> would this warning information will come up.
>
>
>
> Please tell me what’s wrong, Thank you!
>
>
>
> Patch my server.xml for more information:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> SSLEngine="on" />
>
>
>
>
>
>
>
> className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
>
> className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
>
> className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />
>
>
>
>
>
>
>
>
> type="org.apache.catalina.UserDatabase"
>
> description="User database that can be updated and saved"
>
> factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
>
> pathname="conf/tomcat-users.xml" />
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> port="13080"
>
> protocol="org.apache.coyote.http11.Http11NioProtocol"
>
> connectionTimeout="2"
>
> acceptCount="2000"
>
> maxThreads="1200"
>
> minSpareThreads="10"
>
> compression="on"
>
> compressionMinSize="2048"
>
> maxPostSize="10240"
>
> allowTrace="false"
>
> redirectPort="13443"
>
> enableLookups="false"
>
> xpoweredBy="false"
>
>
> compressableMimeType="text/xml,application/octet-stream,application/json"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>port="13089"
>
> protocol="HTTP/1.1"
>
> maxThreads="120"
>
> acceptCount="200"
>
> enableLookups="false"
>
> xpoweredBy="false"
>
> threadPriority="java.lang.Thread#MAX_PRIORITY"
>
> redirectPort="13443" />
>
>
>
>
>
>
> port="13443"
>
> protocol="org.apache.coyote.http11.Http11NioProtocol"
>
> SSLEnabled ="true"
>
> sslProtocol ="TLS"
>
> acceptCount="2000"
>
> minSpareThreads="10"
>
> enableLookups="false"
>
> scheme="https"
>
> secure="true"
>
> clientAuth="false"
>
> keystoreFile="conf/key.store"
>
> keystorePass="oa5l5Azob7HhWOsjJZyjOQ=="
>
>
> ciphers="SSL_RSA_WITH_RC4_128_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA,SSL_RSA_WITH_3DES_EDE_CBC_SHA,SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA,SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA"
>
> maxPostSize="10240"
>
> connectionTimeout="2"
>
> allowTrace="false"
>
> xpoweredBy="false" />
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> failureCount="3" lockOutTime="600"
>
> cacheSize="1000" cacheRemovalWarningTime="3600">
>
>
>
> digest="sha"
>
> resourceName="UserDatabase"/>
>
>
>
>
>
>
>unpackWARs="true" autoDeploy="false" deployOnStartup="false" >
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> directory="logs"
>
> prefix="localhost_access_log." suffix=".txt"
>
> pattern="%h %l %u %t "%r" %s %b" />
>
>
>
>
答复: Re:Tomcat7.0-Setting property 'threadPriority' did not find a matching property
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?
-邮件原件-
发件人: xueshengzj [mailto:xueshen...@163.com]
发送时间: 2012年12月3日 13:36
收件人: Tomcat Users List
主题: Re:Tomcat7.0-Setting property 'threadPriority' did not find a matching
property
Hi, have you seen the error that show it. It tell us that the property is not
matched. The thread priority for threads in the executor, the default is
Thread.NORM_PRIORITY. It should return integer.
在 2012-12-03 12:53:08，Weixiang 写道：
Tomcat version：7.0.29
Question：
I config in my server.xml for a HTTP Connector named “MGMT”:
threadPriority="java.lang.Thread#Thread.MAX_PRIORITY"
When application is starting up，the catalina.out gives some warning information:
WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property
'threadPriority' to 'java.lang.Thread#MAX_PRIORITY' did not find a matching
property.
I search on google and did not get any useful help;
I also search documentation on the apache.org and make sure that
'threadPriority' is a legal attribute for HTTP Connector，so I wonder why would
this warning information will come up.
Please tell me what’s wrong, Thank you!
Patch my server.xml for more information:
魏翔
华为技术有限公司 Huawei Technologies Co., Ltd.
Phone: 025-56620390
Fax:
Mobile: 15850503037
Email: kurt.weixi...@huawei.com
地址：南京市雨花区软件大道101号华为南京研究所 邮编：21
Huawei Technologies Co., Ltd.
RuanJianDaDao, YuHua District,NanJing 21 P.R.China
http://www.huawei.com
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments contain confidential information from HUAWEI,
which
is intended only for the person or entity whose address is listed above. Any
use of the
information contained herein in any way (including, but not limited to, total
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify
the sender by
phone or email immediately and delete it!
