Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 27860 invoked from network); 13 Jul 2009 06:32:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 Jul 2009 06:32:55 -0000 Received: (qmail 99909 invoked by uid 500); 13 Jul 2009 06:33:04 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 99823 invoked by uid 500); 13 Jul 2009 06:33:04 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 99815 invoked by uid 99); 13 Jul 2009 06:33:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jul 2009 06:33:04 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of genspring@gmail.com designates 209.85.198.233 as permitted sender) Received: from [209.85.198.233] (HELO rv-out-0506.google.com) (209.85.198.233) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jul 2009 06:32:55 +0000 Received: by rv-out-0506.google.com with SMTP id b25so842221rvf.55 for ; Sun, 12 Jul 2009 23:32:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=sSiDPEXGza2XOmd7fV94l/Knkf5l2Sc7dz231ozXmbk=; b=hI90f7ZBiLYlYwWB8yQM1EsZIzNdNdx6vhMQo9sqORCRvkWOvK/fXPySdFW0om303h ZexfFlqTxXOC5vw1LiXzWYLRG2POH0YeDAcDM09/rI3QGKYzk/WdIEp6vbxB7QPOEQQb 4aQ3fTSS9BfCks3ZkrHTHDK57iqqRIOvl9kQ0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=NHYBC14soCAtW6xxvaNkYAn9MoZqU/ZvPhzKdGXZLjB9cQiRCP/K6Qg1+I85HKr8Q8 eEQarpy9q7r2Axrxx+iOFoOBWiG7QKI7Wwol5XQX9CYOZgBVslqBhHL3WBLJw4lwtAMX bcdCvaLKBjFjSYEVT6oluerjydWP5VIXwx6zk= MIME-Version: 1.0 Received: by 10.140.191.3 with SMTP id o3mr2454925rvf.91.1247466753478; Sun, 12 Jul 2009 23:32:33 -0700 (PDT) In-Reply-To: References: <5e7fd1eb0906242112m53e14feawf1b17c743fc3793d@mail.gmail.com> Date: Mon, 13 Jul 2009 14:32:33 +0800 Message-ID: Subject: Re: Should we filter those unimportant log out from current server log ? From: Shawn Jiang To: dev@geronimo.apache.org Content-Type: multipart/alternative; boundary=000e0cd14708b5d2af046e907cfa X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd14708b5d2af046e907cfa Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I upload a patch to remove some extra log here: https://issues.apache.org/jira/browse/GERONIMO-4712 Can anyone give any comments ? Thanks in advance. On Thu, Jun 25, 2009 at 1:53 PM, Shawn Jiang wrote: > 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 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 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 > -- Shawn --000e0cd14708b5d2af046e907cfa Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I upload a patch to remove some extra log here:

https://issues.apache.org/jira/= browse/GERONIMO-4712

Can anyone give any comments ?=A0 Thanks in= advance.


On Thu, Jun 25, 2009 at 1:53 PM, Shawn J= iang <genspring= @gmail.com> wrote:
For those log in specific class or package. =A0We can remove them through l= og4j config file.=A0

But for those we want to remove par= t of them in a class. =A0We have to modify the code. =A0I've=A0opened= =A0a=A0JIRA:=A0https://issues.apache.org/jira/browse/GERONIMO-4712=A0to 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 mod= ify 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><= /span> 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. =A0 A= ll these kind of log messages could do is to bury the useful info or to mis= lead the new users.


Some sample of them are:


2009-06-12 16:53:55,171 INFO =A0[Port= letContextManager] Registering 24 portlets for context /console-base=
2009-06-12 16:53:55,203 INFO =A0[PortletContextManager] Por= tlet application with application id '/console-base' already regist= ered.
2009-06-12 16:53:55,203 INFO =A0[PortletContextManager] Reg= istering 24 portlets for context /console-base
2009-06-12 16:53:55,234 INFO =A0[PortletContextManager] Por= tlet application with application id '/console-base' already regist= ered.
2009-06-12 16:53:55,234 INFO =A0[PortletContextManager] Reg= istering 24 portlets for context /console-base
2009-06-12 16:53:55,265 INFO =A0[PortletContextManager] Por= tlet application with application id '/console-base' already regist= ered.
.........


2009-06-23 13:22:36,484 INFO =A0[XSRFHandler]= Created session for uid=3Dnull with sessionId=3D2486E123C24B5E399859E9F5BA= FD95BD, uniqueId=3D-7432393335768912086
2009-06-23 13:22:36,546 INFO =A0[XSRFHandler] Updated HTML = content with XSRF JavaScript for requestURI=3D/


Maybe we could just redirect them to another log = file or just change these kind of message to DEBUG from current INFO. =A0 A= nyway, we must make sure the default log be concise and only contain= important info that users want to know.

Any =A0comments ?

--
Shawn




-- Shawn



--
Shawn
--000e0cd14708b5d2af046e907cfa--