re: jdbcappender: finalize - how to ensure all messages are sent to the database?

Thanks for your reply, Ken, and pointing me in the direction of LogMangager. However, the call to shutdown() does not solve the issue. Shutdown finalizes and closes the appender. That's fine. This can be forced by creating a servlet listener, which, if the web app is destroyed, the listener

Re: JDBCAppender: finalize - how to ensure all messages are sent to the database?

I ran into the same problem with another buffered appender. It appears what you need to do is call the LogManager.shutdown() method before your application exits to clear the buffer. --- Francis Le Monnier <[EMAIL PROTECTED]> wrote: > Simple scenario: > > instantiate logger and appender vars; ad

RE: JDBCAppender - passing parameters to SQL statement

he front of PatternLayout in the config file. Sorry about that. -Original Message- From: Lutz Michael Sent: Wednesday, February 26, 2003 4:40 PM To: 'Log4J Users List' Subject: RE: JDBCAppender - passing parameters to SQL statement Here's an example, working config

Re: JDBCAppender - passing parameters to SQL statement

Hi John, The problem you described is almost the saem I also faced. Apart from MDC (as key value pair per thread basis), I would like to go for custom message rendered through ObjectRenderer. We could not do enough R&D in our team, due to time-constraints upto now. Otherwise I could have managed

RE: JDBCAppender - passing parameters to SQL statement

Wooops, 1 minor correction. "Lgg" shouldn't be on the front of PatternLayout in the config file. Sorry about that. -Original Message- From: Lutz Michael Sent: Wednesday, February 26, 2003 4:40 PM To: 'Log4J Users List' Subject: RE: JDBCAppender - passing pa

RE: JDBCAppender - passing parameters to SQL statement

Here's an example, working config file that includes usage of the JDBC Appender similarly to your example. # ** log4j.rootLogger=DEBUG, myJDBC log4j.appender.myJDBC=org.apache.log4j.jdbc.JDBCAppender log4j.appender.myJDBC.URL=jdbc:microsoft:sqlserver:/

Re: JDBCAppender - Column values

good solution. but i fail to see the need for extending the pattern layout at all. if you can generate the SQL statement and Log message as mentioned below what is the need for a new extended pattern layout ? can you please explain. i am, probably, missing something. Mohan. > as far as i can s

RE: JDBCAppender - Column values

I am a newbie to log4j. Could you please explain how to extend PatternLayout? -Original Message- From: Kevin Steppe [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 23, 2002 2:20 PM To: Log4J Users List Subject: Re: JDBCAppender - Column values LogEvents don't have fields for

Re: JDBCAppender - Column values

LogEvents don't have fields for those items, and the JDBCAppender logs LogEvent objects. So you'll have to do some coding. A couple options off the top of my hand: 1) extend PatternLayout with conversion characters for all those things 2) override getLogStatement(...) in JDBCAppender. 3) creat

RE: JDBCAppender - log connection pooling code to db?

I'm confused about this. I don't want to turn this into a JDBC discussion, but are you saying that some JDBC drivers magically hide *all* connection pooling code somehow, and all I have to worry about is calling getConnection() and closeConnection()? In that case, using JDBCAppender for logging

Re: JDBCAppender problem

You can put the sql statement in the configuration file by doing something like this: http://jakarta.apache.org/log4j/";> -- To unsubscribe, e-mail: For additional commands, e-mail:

RE: JDBCAppender problem

" <[EMAIL PROTECTED]> Subject: RE: JDBCAppender problem

RE: JDBCAppender problem

tLogStatement(org.apache.log4j.spi.LoggingEvent) method allows more explicit control of the statement used for logging -Original Message- From: Jyothi Panduranga [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 10:59 AM To: Log4J Users List Subject: RE: JDBCAppender problem Thanks for your reply. I got myself

RE: JDBCAppender problem

Does anybody have a example configuration file which has a sample parameters for Kevin Steppe's JDBCAppender? Jyothi -Original Message- From: Jyothi Panduranga Sent: Wednesday, June 12, 2002 10:59 AM To: Log4J Users List Subject: RE: JDBCAppender problem Thanks for your reply.

RE: JDBCAppender problem

n file? If not, How do I specify it? Thanks again, Jyothi -Original Message- From: Klein, Scott @ TW [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 10:53 AM To: 'Log4J Users List' Subject: RE: JDBCAppender problem BufferSize, db URL, User, & Password

Re: JDBCAppender problem

Modify JDBCAppender and print out the driver name. Check to see what it's initializing as. Also, make sure the driver is in your classpath. Steve

RE: JDBCAppender problem

BufferSize, db URL, User, & Password are the parameter names - capitalization counts log4j.appender.JDBC=org.apache.log4j.jdbc.JDBCAppender log4j.appender.JDBC.URL=jdbc:odbc:pinjyothi log4j.appender.JDBC.User=pinjyothi log4j.appender.JDBC.Password=jyothi log4j.appender.JDBC.BufferSize=1 -- I do

Re: JDBCAppender - log connection pooling code to db?

Where you override getConnection()/closeConnection() you should call errorHandler.error(...) when you have problems. Bomb Diggy wrote: >Using the JDBCAppender by Kevin Steppe - the one >provided in the 'jdbc' package with 1.2.3. I've >overridden the getConnection() and closeConnection() >me

RE: JDBCAppender - log connection pooling code to db?

To me at seems quite obvious that logging erronous behaviour in a sink to the very same sink is asking for trouble. It's like trying to log to a file that you can't open that file, or to a socket that you can't open the socket. For the same reason Log4j uses LogLog and not itself for internal logg

Re: JDBCAppender performance

At 11:17 08.05.2002 -0700, you wrote: >Ceki, You should look more carefully at getConnection() and >closeConnection(). execute(String sql) calls getConnection() which simply >returns an already open connection. Only when a connection is not yet >open is a new one created. This is an improv

Re: JDBCAppender performance

Performance questions--- First off, databases are pathetically slow compared to file or memory writes. If you have a performance critical application avoid a database where-ever possible. Ironicly, this is true even for database driven applications -- you'll get better performance by reduc

Re: JDBCAppender in 1.2rc1

dded it, rebuilt, and it's now there... > > Mark > > -Original Message- > From: McDowell, Mark [mailto:[EMAIL PROTECTED]] > Sent: Monday, May 06, 2002 8:23 AM > To: 'Log4J Users List' > Subject: RE: JDBCAppender in 1.2rc1 > > I found the jdbc pack

RE: JDBCAppender in 1.2rc1

The build.xml file log4j.jar destination hasn't had the jdbc directory added to it. I added it, rebuilt, and it's now there... Mark -Original Message- From: McDowell, Mark [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 8:23 AM To: 'Log4J Users List' Subject:

RE: JDBCAppender in 1.2rc1

Users List' Subject: RE: JDBCAppender in 1.2rc1 Kevin, I just rebuilt the 1.2rc1 and I don't find a jdbc package... Is that package only in a nightly build release? Mark -Original Message- From: Kevin Steppe [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 4:19 PM To: L

RE: JDBCAppender in 1.2rc1

Kevin, I just rebuilt the 1.2rc1 and I don't find a jdbc package... Is that package only in a nightly build release? Mark -Original Message- From: Kevin Steppe [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 4:19 PM To: Log4J Users List Subject: Re: JDBCAppender in 1.2rc1

RE: JDBCAppender in 1.2rc1

Thanks, Kevin! I'll give that a shot! :) -Original Message- From: Kevin Steppe [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 4:19 PM To: Log4J Users List Subject: Re: JDBCAppender in 1.2rc1 Ceki, could you yank my directory from the contribs as it is now completely out

Re: JDBCAppender in 1.2rc1

Ceki, could you yank my directory from the contribs as it is now completely outdated? Mark, Looks like you are compiling from the contribs/ folder. DONT use the JDBCAppender there. Use the appender in org/apache/log4j/jdbc The example program there (JDBCTest.java) won't work with the new appe

Re: JDBCAppender - using different table def and SQL

So I assume from your question that you understand that the sql string you pass into setSql is just a regular conversion pattern and that all the substitution rules apply, correct? (e.g., "insert into error_log (location, description) values('%c', '%m')", will substitute the message text for %m e

Re: JDBCAppender in Transactions?

A few ideas all around extending JDBCAppender 1) override the getConnection() method. In there you would contact your connection handler (you might have to write one) and grab the active connection. 2) add a new method like: public setConnection(java.sql.Connection c) { connection = c; } A

Re: JDBCAppender in log4j1.2rc1

I was having problems locating JDBCAppender as well. It's not in dist/lib/log4j-1.2rc1.jar . I got the ant build to work, JDBCAppender.class was created, but it's not jar'ed into log4j-1.2rc1.jar. To fix it I added a "${stem}/jdbc/*.class" includes to the ant build target "log4j.jar". D. >

Re: JDBCAppender examples

Set up the JDBCAppender in your config. Then use log4j as you would with any other appender. This is important because you should easily be able to change to logging into a file, JMS sink, console, or database. Here is an example properties file to set up the JDBCAppender as your root appender:

Re: JDBCAppender in log4j1.2rc1

Ron, I suggest you set "jaxp.parser.jar" to xerces c:/ULTIMA/Oracle9iAS/j2ee/home/xerces.jar in build.properties. And try again. Let me know the results. Thanks, Ceki ps: I'll add JDBCAppender to log4j-x.jar. At 12:12 19.04.2002 -0400, you wrote: >I downloaded log4j 1.2rc1 to get use of the

Re: JDBCAppender and Oracle

At 09:49 06.02.2002 -0800, Kevin Steppe wrote: >As a note, sometime this month I'll be giving Ceki a proposed 'official' >JDBCAppender. I would -love- to get suggestions on features. I'd also like >hear what people feel are the advantages of Thomas's Appender (I asked him >directly but he is cur

Re: JDBCAppender and Oracle

nt. > - Joe > > -Original Message- > From: Sankara <[EMAIL PROTECTED]> > To: Log4J Users List <[EMAIL PROTECTED]> > Date: Tuesday, February 05, 2002 11:08 PM > Subject: Re: JDBCAppender and Oracle > > >I am using classes111.zip. but i able to run si

Re: JDBCAppender and Oracle

Sankara <[EMAIL PROTECTED]> To: Log4J Users List <[EMAIL PROTECTED]> Date: Tuesday, February 05, 2002 11:08 PM Subject: Re: JDBCAppender and Oracle >I am using classes111.zip. but i able to run simple jdbc program without any >errors > >Sankar N >- Original

Re: JDBCAppender and Oracle

I am using classes111.zip. but i able to run simple jdbc program without any errors Sankar N - Original Message - From: "Joe Sackett" <[EMAIL PROTECTED]> To: "Log4J Users List" <[EMAIL PROTECTED]> Sent: Tuesday, February 05, 2002 9:00 PM Subject: Re: JDB

Re: JDBCAppender and Oracle

Can you get the full stack trace that winds into the Oracle JDBC driver? That would help diagnose this. I expect, though, that this problem may go away if you install more recent version of the JDBC driver. Which one are you using? classes???.zip - Joe -Original Message- From: Sankara <[

Re: JDBCAppender license

Georg, It is my understanding that all the contributions have to fall under the Apache License (mine certainly does) so you are free to do almost anything with it. Personally I strongly encourage you to subclass as that is one of the most useful features of OO programming -- in fact the JDBCA

Re: JDBCAppender from JMSAppender

ROTECTED]> > To: Log4J Users List <[EMAIL PROTECTED]> > Date: Tuesday, November 20, 2001 9:19 AM > Subject: Re: JDBCAppender from JMSAppender > > > > >Hmm, all this sounds very suspicious to me. There > >should be no problems with composing JMSAppender and &

Re: JDBCAppender from JMSAppender

ork. - Joe -Original Message- From: Ceki Gulcu <[EMAIL PROTECTED]> To: Log4J Users List <[EMAIL PROTECTED]> Date: Tuesday, November 20, 2001 9:19 AM Subject: Re: JDBCAppender from JMSAppender > >Hmm, all this sounds very suspicious to me. There >should be no problems

Re: JDBCAppender from JMSAppender

AIL PROTECTED]> To: Log4J Users List <[EMAIL PROTECTED]> Date: Tuesday, November 20, 2001 9:19 AM Subject: Re: JDBCAppender from JMSAppender > >Hmm, all this sounds very suspicious to me. There >should be no problems with composing JMSAppender and >JDBCAppender. All

Re: JDBCAppender from JMSAppender

Hmm, all this sounds very suspicious to me. There should be no problems with composing JMSAppender and JDBCAppender. All the work is done during serialization of logging event. Have you looked at JMSSink? Regards, Ceki --- Joe Sackett <[EMAIL PROTECTED]> wrote: > I have log4j logging inside of O

RE: JDBCAppender

First off the JDBCAppender is not included in the jar for the distribution. I have tried two JDBCAppenders, Kevin Steppe (found in the distribution in contribs/KevinSteppe) and one referenced on the log4j web page found at http://support.klopotek.de/log4j/jdbc/default.htm. I find Kevin Steppe ea

Re: JDBCAppender

for example with the properties file : log4j.rootCategory=DEBUG, A1 log4j.appender.A1=org.apache.log4j.varia.JDBCAppender Patrick PIERRA "storck"

Re: JDBCAppender

Do you have to use Access? MySQL is available on Windows, so you could use that instead. That error is a JDBC-ODBC bridge error. -Chris - Original Message - From: "Rongmei Rao" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, October 13, 2001 4:20 AM Subject: JDBCAppender H

RE: JDBCAppender upgraded to Log4J 1.1.2

t; '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'; > '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'; > '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'; > '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'; > &

RE: JDBCAppender upgraded to Log4J 1.1.2

Currently I am using a 'DailyFileAppender' that will log messages on a daily basis; using the org.log4j ( and helpers ) package. What I am looking to do is to have a 'JDBCAppender' that will use this same environment ( org.log4j NOT org.apache.log4j ) and also to use some sort of Data Sourcing ins

RE: JDBCAppender upgraded to Log4J 1.1.2

Currently I am using a 'DailyFileAppender' that will log messages on a daily basis; using the org.log4j ( and helpers ) package. What I am looking to do is to have a 'JDBCAppender' that will use this same environment ( org.log4j NOT org.apache.log4j ) and also to use some sort of Data Sourcing ins

Re: JDBCAppender update

I haven't tried it but it should be. All the configuration 'work' is done by the configuration classes in the Log4J framework, so as long as the appender has the appropriate get/set methods and the config file addresses those then it should work 'out of the box' so to speak. Thank Ceki for a pro

Re: JDBCAppender update

Hi, Is it possible to configure the JDBC appender thru the log4j xml config file like other appenders instead of a property file ? thanks ~thomas __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.ya

Re: JDBCAppender update

It should have been attached (at least one person got it) I'll inline it here -- hopefully Netscrape won't kill the format too badly: package org.apache.log4j.varia; import org.apache.log4j.*; import org.apache.log4j.spi.*; import org.apache.log4j.PatternLayout; import org.apache.log4j.helper

Re: JDBCAppender update

Kevein, Sure. I could replace the earlier class if I had the newer version. :-) That was the essence of my previous question. Can you post it? Ceki At 01:22 08.06.2001 -0700, you wrote: >I'm not sure I understand the question really but it is supposed to be an >update to the JDBCAppender I've a

Re: JDBCAppender update

I'm not sure I understand the question really but it is supposed to be an update to the JDBCAppender I've already contributed -- so it belongs to ASF and should replace that earlier class (please could you do that Ceki?). I haven't mentioned it outside of the Log4J list if that's what you mean.

Re: JDBCAppender update

Hi, Is the new JDBCAppender available to the wider public? Ceki At 09:12 05.06.2020 -0700, you wrote: >I spent a lot of time yesterday updating my JDBCAppender. >Looks like that was appropriate timing. > >The new version of my appender has bean-like get/set methods >(plus the now deprecated set

RE: JDBCAppender update

Thanks Kevin! This worked out perfect, I was able to write to database without a problem... -Original Message- From: Kevin [mailto:[EMAIL PROTECTED]] Sent: Friday, June 05, 2020 12:13 PM To: [EMAIL PROTECTED] Subject: JDBCAppender update I spent a lot of time yesterday updating my JDBC

RE: JDBCAppender...

I spy this line in your config. file // Set the priority which messages have to be logged MyCat.setPriority(Priority.INFO); Since you're using MyCat.debug("foo") and the priority is set to INFO, I don't think there will be any output to any appender. Anyone else see different? T

Re: JDBCAppender

Thomas, Thanks for creating JDBCLog.jar. If you would like me to add this to the contribs/ directory, then you must change the Kloptek & Partner AG copyright notice to Apache Software Foundation copyright. According to ASF rules, non-APLed code cannot be added to the CVS repository on Apache

Re: JDBCAppender

It's great to have some discussion on this and I'd love to hear from some others as well. About contributions: I'll put my JDBCAppender in log4j/contributions later today unless Ceki has already done it. I think that perhaps starting up a list of requirements for a JDBCAppender would make sense

Re: JDBCAppender

Hi Oliver, If you would like, I could put up a link on the log4j download pages listing your extension. You should perhaps provide source code as well. Ceki At 16:07 13.02.2001 +0100, you wrote: >Hi, >we have also build an JDBC-Appender for our project (its not the final >release - but i thi

Re: JDBCAppender

I'll try to get it out by the end of this week. I need to test it a little bit more. Kevin Liu Xiao Hua wrote: > Kevin: > > I am also very interested in the JDBCAppender, Where can I get it? > > Thanks a lot! > > Liu Xiaohua > > -Original Message- > From: Kevin Steppe [mailto:[EMAIL P