Return-Path: Delivered-To: apmail-commons-user-archive@www.apache.org Received: (qmail 34250 invoked from network); 3 Jun 2008 01:39:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Jun 2008 01:39:48 -0000 Received: (qmail 24632 invoked by uid 500); 3 Jun 2008 01:39:37 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 24564 invoked by uid 500); 3 Jun 2008 01:39:36 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 24550 invoked by uid 99); 3 Jun 2008 01:39:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jun 2008 18:39:36 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jbm@esonicspider.com designates 69.64.155.193 as permitted sender) Received: from [69.64.155.193] (HELO mail-01.name-services.com) (69.64.155.193) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jun 2008 01:38:45 +0000 Received: from mps-175.microps.com ([207.137.13.175]) by mail-01.name-services.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 2 Jun 2008 18:38:28 -0700 Message-ID: <4844A0B4.8080208@esonicspider.com> Date: Mon, 02 Jun 2008 18:39:00 -0700 From: "John B. Moore" User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Commons Users List Subject: Re: Turning off commons logging References: <48433DEB.7020706@esonicspider.com> <4843AA65.1070500@chello.at> <48444BA4.6060206@esonicspider.com> <1212440150.6253.29.camel@simon-laptop> In-Reply-To: <1212440150.6253.29.camel@simon-laptop> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 03 Jun 2008 01:38:28.0468 (UTC) FILETIME=[85CCEB40:01C8C51A] X-Sender: jbm@esonicspider.com X-Virus-Checked: Checked by ClamAV on apache.org simon wrote: > Again, if you could follow my suggestion and change the output pattern a > little, that would be useful. If the problem messages do not change, > then that proves a different config file is in use. What I had done is to set logging to OFF it turned of my internal code's logging but did not touch the commons logging.. My conclusion was that it was not seeing the config file.. I then moved a copy to the /WEB-INF/classses I then also turn off the logging in that file.. ..no joy.. (and the pattern is different..) My pattern 6450 [http-8080-Processor3](BaseServiceBean.java:240) DEBUG - BaseServiceBean - getPath: IndexPath the commons logging pattern 2008-06-02 17:58:20,901 DEBUG [org.apache.commons.digester.Digester.sax] - endElement(,,web-app) ..with the date and time.. > > Hmm. Mac OSX. Maybe you should check the JVM files themselves, just > because I've never heard of anyone having this problem before and that > is a less-common platform. Didn't java1.5 just get released for Mac a > few weeks ago? Are you using that brand new release? I searched carefully the entire classpath (JBuilder has a view that shows you the entire classpath used on startup) and I did find A general logging.properties file in the: Versions/1.5.0/Home/lib/logging.properties .. with the following settings.. #========================================== # Default global logging level. .level= INFO # default file output is in user's home directory. java.util.logging.FileHandler.pattern = %h/java%u.log java.util.logging.FileHandler.limit = 50000 java.util.logging.FileHandler.count = 1 java.util.logging.FileHandler.formatter = java.util.logging.XMLFormatter # Limit the message that are printed on the console to INFO and above. java.util.logging.ConsoleHandler.level = INFO java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter #============================================ .. which does not seem to be in effect with commons because I'm seeing DEBUG output.. The only other "properties" files I could find in that path had no mention of logging in general or log4j in particular.. (I also used "SpotLight" which searched the entire hard drive and only found what I expected to find and where I expected to find it..) > > There is an option to force commons-logging to output some diagnostics > which *might* be useful in your case. See the link titled > "Troubleshooting guide" on the commons-logging website. Thanks I will review that... > > I'm 95% sure that the issue is that you have another log4j config file > somewhere in your classpath. And that it is NOT inside a commons > jarfile. I wish you where right... so far I have not been able to find such a file.. > > As a last resort, you could edit that commons-logging.properties file to > specify NoOpLog rather than Log4JLog. That should block all messages > logged via commons-logging, although all messages logged directly to > log4j will not be affected. That isn't the best solution of course. That worked.. But you are right not a good solution.. Is there something else I could put in that file that would allow only ERROR messages to come through..? Thanks for your patience and assistance.. John... --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@commons.apache.org For additional commands, e-mail: user-help@commons.apache.org