geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Jiang <genspr...@gmail.com>
Subject Re: Should we filter those unimportant log out from current server log ?
Date Thu, 25 Jun 2009 05:53:12 GMT
For those log in specific class or package.  We can remove them through
log4j config file.
But for those we want to remove part of them in a class.  We have to modify
the code.  I've opened a JIRA:
https://issues.apache.org/jira/browse/GERONIMO-4712 to track this.

On Thu, Jun 25, 2009 at 12:12 PM, Jack Cai <greensight@gmail.com> wrote:

> I agree. Some "INFO" in the current log are not very useful.
>
> Other than changing the log level in the code, another option is to modify
> the default log4j configuration file, which might be easier to do.
>
> -Jack
>
>
> On Tue, Jun 23, 2009 at 11:39 PM, Shawn Jiang <genspring@gmail.com> wrote:
>
>> I believe there are some log that needs to be filtered out from current
>> server log because they are not good/useful information as part of default
>> INFO in log.   All these kind of log messages could do is to bury the useful
>> info or to mislead the new users.
>>
>>
>> Some sample of them are:
>>
>>
>> 2009-06-12 16:53:55,171 INFO  [PortletContextManager] Registering 24
>> portlets for context /console-base
>> 2009-06-12 16:53:55,203 INFO  [PortletContextManager] Portlet application
>> with application id '/console-base' already registered.
>> 2009-06-12 16:53:55,203 INFO  [PortletContextManager] Registering 24
>> portlets for context /console-base
>> 2009-06-12 16:53:55,234 INFO  [PortletContextManager] Portlet application
>> with application id '/console-base' already registered.
>> 2009-06-12 16:53:55,234 INFO  [PortletContextManager] Registering 24
>> portlets for context /console-base
>> 2009-06-12 16:53:55,265 INFO  [PortletContextManager] Portlet application
>> with application id '/console-base' already registered.
>> .........
>>
>>
>> 2009-06-23 13:22:36,484 INFO  [XSRFHandler] Created session for uid=null
>> with sessionId=2486E123C24B5E399859E9F5BAFD95BD,
>> uniqueId=-7432393335768912086
>> 2009-06-23 13:22:36,546 INFO  [XSRFHandler] Updated HTML content with XSRF
>> JavaScript for requestURI=/
>>
>>
>>
>> Maybe we could just redirect them to another log file or just change these
>> kind of message to DEBUG from current INFO.   Anyway, we must make sure the
>> default log be *concise *and only contain important info *that users want
>> to know*.
>>
>> Any  comments ?
>>
>> --
>> Shawn
>>
>
>


-- 
Shawn

Mime
View raw message