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.Thre
-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
-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_PRIOR
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
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?
-邮件原件-
发件人: xueshe
