Return-Path: Delivered-To: apmail-jakarta-avalon-phoenix-dev-archive@apache.org Received: (qmail 24921 invoked from network); 14 Oct 2002 12:20:39 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 14 Oct 2002 12:20:39 -0000 Received: (qmail 12212 invoked by uid 97); 14 Oct 2002 12:21:23 -0000 Delivered-To: qmlist-jakarta-archive-avalon-phoenix-dev@jakarta.apache.org Received: (qmail 12153 invoked by uid 97); 14 Oct 2002 12:21:23 -0000 Mailing-List: contact avalon-phoenix-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon-Phoenix Developers List" Reply-To: "Avalon-Phoenix Developers List" Delivered-To: mailing list avalon-phoenix-dev@jakarta.apache.org Received: (qmail 12128 invoked by uid 98); 14 Oct 2002 12:21:22 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Content-Type: text/plain; charset="iso-8859-1" From: Peter Donald To: "Avalon-Phoenix Developers List" Subject: Re: Logging still broken in nightly release 2002-10-13 Date: Mon, 14 Oct 2002 22:26:28 +1000 User-Agent: KMail/1.4.2 References: <001901c27356$c4e6d8c0$50051c0a@marketmaker.de> In-Reply-To: <001901c27356$c4e6d8c0$50051c0a@marketmaker.de> X-Wisdom: A right is not what someone gives you; it's what no one can take from you. MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200210142226.28124.peter@apache.org> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Mon, 14 Oct 2002 17:53, Oliver Flege wrote: > Hi, > > > -----Original Message----- > > From: Paul Hammant [mailto:Paul_Hammant@yahoo.com] > > Sent: Sunday, October 13, 2002 10:49 PM > > To: Avalon-Phoenix Developers List > > Subject: Phoenix nightly > > http://jakarta.apache.org/builds/jakarta-avalon-phoenix/nightly/2002-10= -13/ > ... > > > Can those that had logging concerns please test this one.. > > Logging is still broken, everything is logged using the default categor= y. I can't reproduce the problem. Can you download http://jakarta.apache.org/~donaldp/avalon-demo.sar.zip rename it to avalon-demo.sar and place it in $PHOENIX_HOME/apps and then=20 startup phoenix. You should see two log files created avalon-demo.log and= =20 thread-manager.log and both should have content in them. (thread-manager.= log=20 has all the logs for thread-manager block and avalon-demo.log has all the= =20 rest). If you don't have this can you make sure you downloaded the archive from=20 http://jakarta.apache.org/builds/jakarta-avalon-phoenix/nightly/2002-10-1= 3/ If that still does not help then can you send me an example which fails=20 (especially the environment.xml). > I started phoenix with the -d option and got some debug log messages > telling me that the environment.xml is parsed correctly: > DEBUG 2002-10-14 09:34:35.108 [Phoenix.] (): added logger for categor= y > foo thats fine. > but the log file does not contain any messages indicating the logger fo= r > the respective category is ever returned ("Logger for category foo > returned"), which it should if everything would work correctly. Thats also fine. Phoenix grabs the DefaultLogger and then uses that to aq= uire=20 other loggers so you will never see "Logger for category foo returned" in= the=20 logs. --=20 Cheers, Peter Donald *------------------------------------------------------* | "Common sense is the collection of prejudices | | acquired by age 18. " -Albert Einstein | *------------------------------------------------------*=20 -- To unsubscribe, e-mail: For additional commands, e-mail: