RE: JDBCAppender

Have you attached the appender to any logger? Heri > -Original Message- > From: Simonebernardi [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 08, 2008 12:12 PM > To: log4j-user@logging.apache.org > Subject: [SPAM (DNS Blacklist)] - JDBCAppender - Sending mail server > found on list.dsbl.o

Re: JDBCAppender

Yes     Bender Heri ha scritto: Have you attached the appender to any logger? Heri -Original Message- From: Simonebernardi [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 08, 2008 12:12 PM To: log4j-user@logging.apache.org Subject: [SPAM (DNS Blacklist)] -

RE: JDBCAppender

> From: Green, Kay [mailto:kay.gr...@mckesson.com] > WARNING: This version of JDBCAppender is very likely to be completely > replaced in the future. Moreoever, it does not log exceptions. > Does anyone know if this appender has been replaced or is in the process > of being replaced? Hi Kay, People

RE: JDBCAppender help

http://www.dankomannhaupt.de/projects/ -Original Message- From: Harper, Allen (AHARPER) [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 09, 2005 6:42 PM To: Log4J Users List Subject: JDBCAppender help Can anyone please send me an example using the current implementation of the JDBCAp

RE: JDBCAppender help

Thank you! Al -Original Message- From: WYNIWYG MOUAWAD Philippe (CAMPUS) [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 09, 2005 11:44 AM To: Log4J Users List Subject: RE: JDBCAppender help http://www.dankomannhaupt.de/projects/ -Original Message- From: Harper, Allen

Re: JDBCAppender replacement

1.3 has a replacement (DBAppender). On Apr 5, 2005 11:09 AM, John Ferron <[EMAIL PROTECTED]> wrote: > I'm curious as to when the JDBCAppender class is slated to be replaced > in the current implemenation of Log4j. I saw that there is an > implemention by http://www.dankomannhaupt.de/projects/.

Re: JDBCAppender replacement

And when is 1.3 going to be a stable production release? >>> [EMAIL PROTECTED] 4/5/2005 11:22:11 AM >>> 1.3 has a replacement (DBAppender). On Apr 5, 2005 11:09 AM, John Ferron <[EMAIL PROTECTED]> wrote: > I'm curious as to when the JDBCAppender class is slated to be replaced > in the current imp

Re: JDBCAppender replacement

I don't know when it will be released. Probably "when it is ready". :-) On Apr 5, 2005 11:26 AM, John Ferron <[EMAIL PROTECTED]> wrote: > And when is 1.3 going to be a stable production release? > > >>> [EMAIL PROTECTED] 4/5/2005 11:22:11 AM >>> > 1.3 has a replacement (DBAppender). > > On Apr

RE: JDBCAppender replacement

PROTECTED] Tel: (+574)4355596, Medellin - Colombia -Mensaje original- De: James Stauffer [mailto:[EMAIL PROTECTED] Enviado el: Martes, 05 de Abril de 2005 11:45 a.m. Para: Log4J Users List Asunto: Re: JDBCAppender replacement I don't know when it will be released. Probably &qu

Re: JDBCAppender replacement

Email: [EMAIL PROTECTED] > Tel: (+574)4355596, Medellin - Colombia > > -Mensaje original- > De: James Stauffer [mailto:[EMAIL PROTECTED] > Enviado el: Martes, 05 de Abril de 2005 11:45 a.m. > Para: Log4J Users List > Asunto: Re: JDBCAppender replacement > > >

RE: JDBCAppender configuration

Johannes Hoechstaedter [mailto:[EMAIL PROTECTED] wrote > I am up to build a coocon webapplication, and I am using the > JDBCAppender for logging. It works quite well. My only problem is, that > when I switch on the loggin in debug mode, my application is as fast as > a snail because of the heavy da

RE: JDBCAppender configuration

> The JDBCAppender is shoddy anyhow - write yourself a replacement. It's a > great way to learn about what makes a good Appender. To follow up: what I tend to do is have a custom JDBC Appender that adds a small custom log entry object (with all interesting info from the LoggingEvent) to a limit

Re: JDBCAppender configuration

Johannes Hoechstaedter skrev den 15-07-2008 16:20: Hi everybody, I am up to build a coocon webapplication, and I am using the JDBCAppender for logging. It works quite well. My only problem is, that when I switch on the loggin in debug mode, my application is as fast as a snail because of the

Re: JDBCAppender configuration

Michael Erskine schrieb: The JDBCAppender is shoddy anyhow - write yourself a replacement. It's a great way to learn about what makes a good Appender. To follow up: what I tend to do is have a custom JDBC Appender that adds a small custom log entry object (with all interesting info from t

Re: JDBCAppender configuration

Thorbjørn Ravn Andersen schrieb: Johannes Hoechstaedter skrev den 15-07-2008 16:20: Hi everybody, I am up to build a coocon webapplication, and I am using the JDBCAppender for logging. It works quite well. My only problem is, that when I switch on the loggin in debug mode, my application is

RE: JDBCAppender problem

Hi Aleksandar, Had a quick look at the config and everything else, they do seem fine... Can you do the following and get back ? 1. Connect to DB and try manually inserting a record using the username and id specified? 2. i see the table name as "logs" can you try changing this to "LOGS".. some

Re: JDBCAppender and DB passwords

There's a couple ways. Both involve referencing variables set externally. For instance... ${db.username} ${db.password) You can make these variables available in one of two ways (only the first way below if you are using XML config) 1. Set it as a system property. e.g... java -Ddb.

Re: JDBCAppender to MS Access Database

It should be doable with the OJDBC driver... Slow and definitively not a smart idea ... IMHO but it should work \T, -- Any fool can write code that a computer can understand. Good programmers write code that humans can understand. Martin Fowler

Re: JDBCAppender with large message values

Hi, > Hi, > > I want to include the JDBCAppender as one of our appenders so that all > error level messages will be written to a common database. The problem is > that the message content frequently contains a stack trace which is too > large for the database column. What I get right now is a ro

RE: JDBCAppender with large message values

e that string rendered somehow??? -Original Message- From: Mattias Andersson [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 19, 2006 5:52 AM To: Log4J Users List Subject: Re: JDBCAppender with large message values Hi, > Hi, > > I want to include the JDBCAppender as one of our appenders so

Re: JDBCAppender fails to pass connection URL string

AFK, sorry for the top-post. Have you looked at our unit tests? There might be something there to help see what the usage pattern is for JNDI. Gary On Tue, Dec 10, 2019, 06:02 Alban Hertroys < alban.hertr...@apollovredestein.com> wrote: > Hi, > > We're having a lot of trouble getting the JDBCApp

Re: JDBCAppender fails to pass connection URL string

I just looked at the JDBC unit tests and surprisingly didn’t see any that use a configuration file. Ralph > On Dec 12, 2019, at 7:54 AM, Matt Sicker wrote: > > Unit tests in the log4j project. All our components have examples in unit > tests. > > On Thu, Dec 12, 2019 at 04:26 Alban Hertroys <

Re: JDBCAppender fails to pass connection URL string

http://logging.apache.org/log4j/2.x/manual/appenders.html#JDBCAppender does have sample configurations but there is not one with the configuration I would expect to use where you can specify the driver class, user name and

Re: JDBCAppender fails to pass connection URL string

The more: https://github.com/apache/logging-log4j2/tree/release-2.x/log4j-core/src/test/resources/org/apache/logging/log4j/core/appender/db/jdbc Gary On Thu, Dec 12, 2019 at 3:54 PM Gary Gregory wrote: > On Thu, Dec 12, 2019 at 9:55 AM Ralph Goers > wrote: > >> I just looked at the JDBC unit

Re: JDBCAppender fails to pass connection URL string

On Thu, Dec 12, 2019 at 9:55 AM Ralph Goers wrote: > I just looked at the JDBC unit tests and surprisingly didn’t see any that > use a configuration file. > Here is a 'fancy' example (the kind of stuff I use at work): https://github.com/apache/logging-log4j2/blob/release-2.x/log4j-jdbc-dbcp2/sr

Re: Re: JDBCAppender fails to pass connection URL string

"Gary Gregory" wrote on 2019-12-11 22:01:54: > CAUTION : External email. Do not click links or open attachments > unless you recognize the sender and know the content is safe. > > AFK, sorry for the top-post. Have you looked at our unit tests? There might > be something there to help see what

Re: Re: JDBCAppender fails to pass connection URL string

Unit tests in the log4j project. All our components have examples in unit tests. On Thu, Dec 12, 2019 at 04:26 Alban Hertroys < alban.hertr...@apollovredestein.com> wrote: > "Gary Gregory" wrote on 2019-12-11 22:01:54: > > > CAUTION : External email. Do not click links or open attachments > > u

Betr: Re: JDBCAppender fails to pass connection URL string

"Ralph Goers" wrote on 2019-12-12 16:00:02: > http://logging.apache.org/log4j/2.x/manual/appenders.html#JDBCAppender < > http://logging.apache.org/log4j/2.x/manual/appenders.html#JDBCAppender > > does have sample configurations but there is not one with the > configuration I would expect to use

Betr: Re: JDBCAppender fails to pass connection URL string

"Gary Gregory" wrote on 2019-12-12 21:54:27: > The more: > > https://github.com/apache/logging-log4j2/tree/release-2.x/log4j- > core/src/test/resources/org/apache/logging/log4j/core/appender/db/jdbc > > Gary Thanks for the examples, much appreciated. It confirmed that I was probably doing th

Betr: Betr: Re: JDBCAppender fails to pass connection URL string

t;Context contains " + rows + " items."); } } "Alban Hertroys" wrote on 2019-12-12 17:20:26: > Van: "Alban Hertroys" > Aan: "Log4J Users List" > Datum: 2019-12-12 17:20 > Onderwerp: Betr: Re: JDBCAppender fails to pass connectio

Re: Betr: Re: JDBCAppender fails to pass connection URL string

No, it doesn’t necessarily mean that. Some of the unit tests configure things programmatically by directly calling the plugins. If you look at the documentation you will see and as connection sources you can configure. You should try that. I don’t know why examples weren’t added to the doc o