Return-Path: Delivered-To: apmail-db-torque-user-archive@www.apache.org Received: (qmail 72054 invoked from network); 31 Jul 2008 15:29:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Jul 2008 15:29:49 -0000 Received: (qmail 36756 invoked by uid 500); 31 Jul 2008 15:29:47 -0000 Delivered-To: apmail-db-torque-user-archive@db.apache.org Received: (qmail 36742 invoked by uid 500); 31 Jul 2008 15:29:47 -0000 Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Apache Torque Users List" Reply-To: "Apache Torque Users List" Delivered-To: mailing list torque-user@db.apache.org Received: (qmail 36731 invoked by uid 99); 31 Jul 2008 15:29:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jul 2008 08:29:47 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [64.115.63.149] (HELO unix49.broadviewnet.net) (64.115.63.149) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 31 Jul 2008 15:28:51 +0000 Received: (qmail 4712 invoked by uid 32008); 31 Jul 2008 15:38:52 -0000 X-Originating-IP: 64.115.227.187 Received: from unknown (HELO DLEX01.datalinx.net) (64.115.227.187) by unix49.broadviewnet.net with SMTP; 31 Jul 2008 15:38:52 -0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C8F322.32D08A7E" Subject: RE: Log4J + Torque ... gonna drive me mad. Date: Thu, 31 Jul 2008 11:29:18 -0400 Message-ID: <35DBF5C7E3C79B44A7753CFFF51753AD0184D8F6@DLEX01.datalinx.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: <35DBF5C7E3C79B44A7753CFFF51753AD0184D8F6@DLEX01.datalinx.net> Thread-Topic: Log4J + Torque ... gonna drive me mad. Thread-Index: AcjzIK4k4oN/GU1TTyCBLqONJjHj1gAAFAn1 References: <166af1cf0807310059x6b95c7b8ie07b65e89363fed4@mail.gmail.com><361943.50737.qm@web50808.mail.re2.yahoo.com> <166af1cf0807310816n12f68b9am59230f5c36b09274@mail.gmail.com> From: "Naveen Murthy" To: "Apache Torque Users List" X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C8F322.32D08A7E Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Actually, i dont think those 2 lines coming on ur stdout means - "log4j will not work for you" it just means soemhwere, some code is trying to load a=20 log4j config file , which doesnt exist. I can assure u its not fatal, and other apps can continue to use log4j as long as they provide it with their correct log4j config file. i see that in my aplication also, may be some 3rd party jar is failing to provide log4j config. Yet i do my log4j init() and everything works fine and it spits out the log as required. just foll the basic guideliens..may be itll help 1. import the log4j stuff 2. declare ur logger ---> public static Logger errorLog =3D null; 3. Init the log4j properties..(either from a jar, or file ..whatever = resource) InputStream is =3D = xxxBean.class.getClassLoader().getResourceAsStream("/conf/xxx_logging.pro= perties"); Properties props =3D new Properties(); props.load(is); PropertyConfigurator.configure(props); =20 4. aquire the logger. errorLog =3D Logger.getLogger("xxx.ERRORLOG"); //make sure prperty file = has this declared... 5. carry on logging!! errorLog.error(" Naming exception in create() of MDB, error loading = configuration info."); hope this helps... Naveen -----Original Message----- From: Shinkan [mailto:shinkan@gmail.com] Sent: Thu 7/31/2008 11:16 AM To: Apache Torque Users List; alvarocoronel67@yahoo.com Subject: Re: Log4J + Torque ... gonna drive me mad. =20 It's a really sad day for all those mates (owh, come on, I'm pretty sure there's thousand) who have been following this story. I've expanded all my .jar libs on a folder. Then I searched for all ".properties" files. No log4j.properties ... and the only file that mention "log4j" = properties variables is a default one in the log4j .jar. (Exactly, defaultconfig.properties in org\apache\log4j\lf5\config, in log4j_(version).jar -- doesn't seem that it can affect) I'm running out of ideas... (especially that for now I only use YOURS = ...) On Thu, Jul 31, 2008 at 16:41, Alvaro Coronel = wrote: > Yep. I think there's another log4j.properties somewhere. Coming to = think > about it, maybe there are several, with all those pesky, verbose = libraries > we get advantage of. > > You running Unix? Try the suggested commands. > The Windows equivalent would be to expand all the .jar files (easily = done > using multiple-selection and WinRAR), then run a Search on the = resulting > folder tree. > > Go ahead Shinkan, by now I really want to know if there's another > log4j.properties file somewhere in those jars. > > Best of luck, > =C1lvaro > ------_=_NextPart_001_01C8F322.32D08A7E Content-Type: text/plain; charset=us-ascii --------------------------------------------------------------------- To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org For additional commands, e-mail: torque-user-help@db.apache.org ------_=_NextPart_001_01C8F322.32D08A7E--