Re: Dynamic Update of Log Priority

Hi,

On 9/5/07, Rottgardt, Jens (K-SOB-2/3) <[email protected]> wrote:
> Hi Simon,
>
> thanks for your fast reply. It works. So what I do now is the following
>
> public void changeJMXLogging(int newPriority)
> {
>         Log.setDefaultPriority(newPriority);
>         Log.redirectTo(null);
> }
>
>
> One more question. The doc sayes the default log priority is WARN. But
> calling log.getDefaultPriority() after system start returns INFO. So which
> priority I shall use to "reset" set the logging to default WARN or INFO ?

I guess INFO. I used warn level at the beginning, then changed to
info. Can you please file a bug about this ?

Thanks,

Simon
-- 
http://bordet.blogspot.com

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/