Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 47625 invoked from network); 20 Sep 2006 19:56:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Sep 2006 19:56:43 -0000 Received: (qmail 51476 invoked by uid 500); 20 Sep 2006 19:56:38 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 51415 invoked by uid 500); 20 Sep 2006 19:56:38 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 51404 invoked by uid 99); 20 Sep 2006 19:56:38 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Sep 2006 12:56:38 -0700 Authentication-Results: idunn.apache.osuosl.org header.from=erron.austin@gmail.com; domainkeys=good X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=DNS_FROM_RFC_ABUSE,HTML_30_40,HTML_MESSAGE,RCVD_BY_IP DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 Received: from [66.249.82.232] ([66.249.82.232:36827] helo=wx-out-0506.google.com) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id D1/DC-01963-1FC91154 for ; Wed, 20 Sep 2006 12:56:33 -0700 Received: by wx-out-0506.google.com with SMTP id s10so394078wxc for ; Wed, 20 Sep 2006 12:56:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=HlDJGprPzBkUB2t4sGWReDeMY9tBazdbvnopkKxWCXx7NlBXm669jCKdpQ5e6364QrO5OLTZoujZRhGF+N7HLHp3LZNv4M1BPow5CkviU3UDx2ayhXVNgTS5OymckvRhXiZjE5E2lz/A9TwWFqjTA8+eBq8Z7v2HqA0Krn6OjaE= Received: by 10.70.83.4 with SMTP id g4mr25281827wxb; Wed, 20 Sep 2006 12:56:30 -0700 (PDT) Received: by 10.70.94.20 with HTTP; Wed, 20 Sep 2006 12:56:30 -0700 (PDT) Message-ID: Date: Wed, 20 Sep 2006 15:56:30 -0400 From: "Erron Austin" To: users@cocoon.apache.org Subject: Re: Restricting Logging In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_362099_4384644.1158782190139" References: X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_362099_4384644.1158782190139 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Well, never mind. Anyone solve this? On 9/20/06, Erron Austin wrote: > > I added to my jboss-web.xml to get > rid of these messages. > > > On 5/23/06, Andrew Stevens wrote: > > > > >From: "Victoria Vitaver" > > >Date: Tue, 23 May 2006 12:39:33 +1000 > > > > > >Hi, > > > > > >I am having trouble changing the logkit.xconf to restrict logging of > > cocoon > > >messages. I have tried to look for 'howtos' but since logkit was a part > > of > > >the now 'closed' avalon project I really cant dig up resources on it. > > > > It's not that much different to log4j configuration IMO. The targets > > are > > like log4j's appenders and the categories are like log4j's loggers. > > > > >What is happening is this: we are running cocoon 2.1.9 with jboss, and > > >cocoon.log gets written in the > > >tmp/ directory. I want to be able to specify a 'WARN' level minimum for > > all > > >messages in this log. I cant figure out how to do it though. > > > > You can either (by comparison with the error file target) use a > > priority-filter with log-level="WARN", or change the log-level of any > > categories that use that log-target. I'd be more specific, but I've > > only > > got a 2.1.7 xconf file in front of me and it doesn't even mention a > > cocoon.log file. YMMV. > > > > >Also, my server.log contains a million messages of this form : > > > > > >2006-05-23 12:19:41,582 DEBUG [net.sf.ehcache.Cache ] cocoon-ehcache-1: > > Is > > >element with key > > > > >PK_R-resource-resource://org/apache/cocoon/forms/resources/css/forms.css > > >expired?: false > > >2006-05-23 12:19:41,605 DEBUG [net.sf.ehcache.store.MemoryStore] > > >cocoon-ehcache-1Cache: MemoryStore hit for > > > > >PK_R-resource-resource://org/apache/cocoon/forms/resources/css/forms-calenda > > >r.css > > > > > >does anyone have any idea how or where I can also restrict these > > messages > > >to > > >'INFO' level? > > > > Assuming server.log is another Cocoon log file (again, I don't see that > > one > > in my 2.1.7 configuration), the same should apply. Just add a > > priority-filter with log-level="INFO" to the target, or increase the > > log-level of any categories that use it. If it's a standard JBoss log > > file, > > not one of Cocoon's, presumably there's a log factory configured to > > write to > > the standard output and JBoss captures that. > > > > Sorry I can't be more help. > > > > > > Andrew. > > > > > > > >Thanks, > > > > > >Vica > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org > > For additional commands, e-mail: users-help@cocoon.apache.org > > > > > ------=_Part_362099_4384644.1158782190139 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Well, never mind. 
 
Anyone solve this?

 
On 9/20/06, Erron Austin <erron.austin@gmail.com> wrote:
I added <category log-level="ERROR" name=""/> to my jboss-web.xml to get rid of these messages.


On 5/23/06, Andrew Stevens <ats37@hotmail.com > wrote:
>From: "Victoria Vitaver" < victoria@tt.com.au>
>Date: Tue, 23 May 2006 12:39:33 +1000
>
>Hi,
>
>I am having trouble changing the logkit.xconf to restrict logging of cocoon
>messages. I have tried to look for 'howtos' but since logkit was a part of
>the now 'closed' avalon project I really cant dig up resources on it.

It's not that much different to log4j configuration IMO.  The targets are
like log4j's appenders and the categories are like log4j's loggers.

>What is happening is this: we are running cocoon 2.1.9 with jboss, and
>cocoon.log gets written in the
>tmp/ directory. I want to be able to specify a 'WARN' level minimum for all
>messages in this log. I cant figure out how to do it though.

You can either (by comparison with the error file target) use a
priority-filter with log-level="WARN", or change the log-level of any
categories that use that log-target.  I'd be more specific, but I've only
got a 2.1.7 xconf file in front of me and it doesn't even mention a
cocoon.log file.  YMMV.

>Also, my server.log contains a million messages of this form :
>
>2006-05-23 12:19:41,582 DEBUG [net.sf.ehcache.Cache ] cocoon-ehcache-1: Is
>element with key
>PK_R-resource-resource://org/apache/cocoon/forms/resources/css/forms.css
>expired?: false
>2006-05-23 12:19:41,605 DEBUG [net.sf.ehcache.store.MemoryStore ]
>cocoon-ehcache-1Cache: MemoryStore hit for
>PK_R-resource-resource://org/apache/cocoon/forms/resources/css/forms-calenda
>r.css
>
>does anyone have any idea how or where I can also restrict these messages
>to
>'INFO' level?

Assuming server.log is another Cocoon log file (again, I don't see that one
in my 2.1.7 configuration), the same should apply.  Just add a
priority-filter with log-level="INFO" to the target, or increase the
log-level of any categories that use it.  If it's a standard JBoss log file,
not one of Cocoon's, presumably there's a log factory configured to write to
the standard output and JBoss captures that.

Sorry I can't be more help.


Andrew.

>
>Thanks,
>
>Vica



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org



------=_Part_362099_4384644.1158782190139--