-----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
