Return-Path: Delivered-To: apmail-logging-log4j-user-archive@www.apache.org Received: (qmail 24795 invoked from network); 15 Jun 2005 04:30:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Jun 2005 04:30:56 -0000 Received: (qmail 7323 invoked by uid 500); 15 Jun 2005 04:30:52 -0000 Delivered-To: apmail-logging-log4j-user-archive@logging.apache.org Received: (qmail 7253 invoked by uid 500); 15 Jun 2005 04:30:51 -0000 Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Users List" Reply-To: "Log4J Users List" Delivered-To: mailing list log4j-user@logging.apache.org Received: (qmail 7207 invoked by uid 99); 15 Jun 2005 04:30:51 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from mail.comotivsystems.com (HELO pdxcorp1.vwsnet.com) (128.241.65.66) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 14 Jun 2005 21:30:45 -0700 X-MIMEOLE: Produced By Microsoft Exchange V6.0.6249.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C57162.F702ED28" Subject: RE: CustomSQLDBReceiver Date: Tue, 14 Jun 2005 21:30:31 -0700 Message-ID: <984A7225EFC7FD44B0B66D3A29A14400061D24@pdxcorp1.vwsnet.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: <984A7225EFC7FD44B0B66D3A29A14400061D24@pdxcorp1.vwsnet.com> Thread-Topic: CustomSQLDBReceiver thread-index: AcVxXMtkSDMVmbqETeqMPNdcXnSgPAABeEGP From: "Scott Deboy" To: "Log4J Users List" X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C57162.F702ED28 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable You need to use the latest version of build.xml in cvs instead of the = one included with log4j 1.3alpha 6. You can download it here: http://cvs.apache.org/viewcvs.cgi/logging-log4j/build.xml?rev=3D1.161&vie= w=3Dmarkup Right-click the download link and save. Replace the build.xml at the = root of the log4j 1.3alpha6 tar.gz with this new build.xml, then re-run = the db target. Scott -----Original Message----- From: Tan Kah Siong [mailto:jax79sg@yahoo.com.sg] Sent: Tue 6/14/2005 8:46 PM To: Log4J Users List Cc:=09 Subject: RE: CustomSQLDBReceiver Hi, i recompiled a log4j-db (ant log4j-db.jar) from the given link. Overwrote the jar to Chainsaw folder and added jar to -classpath. It still has same error. Pls advise.=20 --- Scott Deboy wrote: > CustomSQLDBReceiver was left out of the db jar in > the 1.3 alpha 6 release because of a problem with > the ant script. =20 >=20 > I've fixed the ant problem so if you feel like > building from CVS, the db jar will contain the > class. >=20 > The class is available with the 1.3 alpha 6 download > - in src/java/org/apache/log4j/db - You could > compile it and add it to your classpath set in > chainsaw.bat, and it should work ok. =20 >=20 > 1.3 alpha 6 is available here: > http://logging.apache.org/site/binindex.cgi >=20 > Scott >=20 > -----Original Message----- > From: Tan Kah Siong [mailto:jax79sg@yahoo.com.sg] > Sent: Tue 6/14/2005 6:00 PM > To: Log4J Users List > Cc:=09 > Subject: RE: CustomSQLDBReceiver > I had followed the instructions to loading the > config > file. I had the error encountered attached. > It seems that the SQLreceiver class cannot be found. >=20 > The program was run using the provided chainsaw.bat. >=20 > Thanks >=20 > --- Scott Deboy wrote: >=20 > > 1. The file-load menu items are provided as a way > to > > process a log file created by a file appender > > configured to use XMLLayout. > >=20 > > Instead, configure Chainsaw this way: > >=20 > > Open Chainsaw > > Select the view-show application wide preferences > > menu > >=20 > > In the 'automatic configuration url' field at the > > bottom, specify the URL to your config file.=20 > > Example: file:///c:/mysql-chainsaw-config.xml > >=20 > > Restart Chainsaw > >=20 > > 2. Chainsaw does support custom fields and > > CustomSQLDBReceiver provides a way to pass them to > > Chainsaw. Customsqldbreceiver expects all > > properties to be combined into a single string and > > returned as the PROPERTIES field in the SQL > > statement. This field is then parsed into the > > individual properties, thus the need for concat. =20 > > Ugly but it works. If you feel like contributing > a > > patch to improve the receiver in this area, please > > do! > >=20 > > 3. There is a JNDIConnectionSource, which can be > > pooled. See > > > http://logging.apache.org/log4j/docs/api-1.3/org/apache/log4j/db/JNDIConn= ectionSource.html > >=20 > > Scott > >=20 > > -----Original Message----- > > From: Tan Kah Siong [mailto:jax79sg@yahoo.com.sg] > > Sent: Tue 6/14/2005 2:12 AM > > To: log4j-user@logging.apache.org > > Cc:=09 > > Subject: CustomSQLDBReceiver > > Hi, > >=20 > > I am interested in using my mssql server as a base > > for > > Chainsaw log viewer. > >=20 > > I had tried to do this after reading the > > documentation > > and encountered the following problems and > > questions. > >=20 > > I had edited the Example Receiver configuration by > > deleting away all plugins except CustomDBReceiver. > I > > also changed the connection source's password, > user, > > driver and url to my requirements. Lastly i used a > > sql > > statement that would utilise the compulsary fields > > as > > stated in the documentation, without the concat > > part. > > The sql server i used is setup with the > > corresponding > > fields. > >=20 > > I fired up ChainSaw and loaded the edited xml file > > through the "Load Log4J File" menu, however, > nothing > > happens after that, no loading nor errors. I also > > see > > no network activity that indicates attempts to > > contact > > sql server.=20 > >=20 > > 1) Is there any step i missed or gone wrong? > >=20 > > 2) I noted that chainsaw support only the > documented > > fields, can it support other custom fields. ?Using > > concat? > >=20 > > 3) How would i use pooled connections with > ChainSaw? > >=20 > > Please advice. > >=20 > >=20 > > =09 > > __________________________________=20 > > Discover Yahoo!=20 > > Use Yahoo! to plan a weekend, have fun online and > > more. Check it out!=20 > > http://discover.yahoo.com/ > >=20 > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > log4j-user-unsubscribe@logging.apache.org > > For additional commands, e-mail: > > log4j-user-help@logging.apache.org > >=20 > >=20 > >=20 > >=20 > >=20 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > log4j-user-unsubscribe@logging.apache.org > > For additional commands, e-mail: > log4j-user-help@logging.apache.org >=20 >=20 > =09 > __________________________________=20 > Discover Yahoo!=20 > Get on-the-go sports scores, stock quotes, news and > more. Check it out!=20 > http://discover.yahoo.com/mobile.html >=20 >=20 >=20 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > log4j-user-unsubscribe@logging.apache.org > For additional commands, e-mail: log4j-user-help@logging.apache.org =09 __________________________________=20 Yahoo! Mail=20 Stay connected, organized, and protected. Take the tour:=20 http://tour.mail.yahoo.com/mailtour.html=20 --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-user-help@logging.apache.org ------_=_NextPart_001_01C57162.F702ED28 Content-Type: text/plain; charset=us-ascii --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-user-help@logging.apache.org ------_=_NextPart_001_01C57162.F702ED28--