PatternLayout extensions & Log4j JDBCAppender

[Kevin Steppe <ks...@pacbell.net>]

After digging into the throwable info in a JDBCAppender a littler here 
is my current idea:

Use an extension to the PatternLayout, which can convert the throwable 
into a single string (with colons, or \n, or whatever in between).  This 
new conversion character code then be placed in the normal sql such as:
insert into log (message, trace) values ('%m', '%throw')

I remeber reading that custom conversions are fairly easy.  Anyone have 
a pointer for me?

Kevin


Ceki Gülcü wrote:

>
> At 10:47 06.06.2002 -0700, you wrote:
>
>> I ran some tests to generate errors in flushBuffer() [lines 226-280]. 
>> The first instance of errorHandler.error generated some console 
>> output. The second instance (line 267) did not generate anything.  I 
>> did not specify any particular errorHandler.  When I placed a 
>> System.out.println inside that catch block I got it's output.  Thus 
>> it appears that by default the error call on line 267 will not 
>> generate output.
>>
>> Could you advise me or look at what is happening here?
>
>
> Does OnlyOnceErrorHandler ring a bell? :-)
>
>> Re: Bug --
>> No, the last JDBCAppender I sent you did not fix the bug.  I am 
>> working on that right now.
>
>
> Excellent. I am looking forward for the resolution of this bug.
>
>
> -- 
> Ceki
>
> SUICIDE BOMBING - A CRIME AGAINST HUMANITY
> Sign the petition: http://www.petitiononline.com/1234567b
> I am signatory number 22106. What is your number?
>
>
> -- 
> To unsubscribe, e-mail:   
> <ma...@jakarta.apache.org>
> For additional commands, e-mail: 
> <ma...@jakarta.apache.org>
>
>



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: PatternLayout extensions & Log4j JDBCAppender

[Ceki Gülcü <ce...@qos.ch>]

There is an example in examples/ directory. Adding a new conversion
character is indeed a natural continuation of your current approach
which I must say is ill advised.

Escaping quotes is one issue that PreparedStatements solve trivially.
PreparedStatements are a mandatory part of the JDBC spec while Batch
statements are optional.  MySQL does support PreparedStatements.

Log4j components have to be absolutely reliable. There are many cool
features that we do not implement because they cannot be implemented
reliably. JDBCAppender must adhere to the same guidelines.

At 11:47 06.06.2002 -0700, Kevin Steppe wrote:
>After digging into the throwable info in a JDBCAppender a littler here is 
>my current idea:
>
>Use an extension to the PatternLayout, which can convert the throwable 
>into a single string (with colons, or \n, or whatever in between).  This 
>new conversion character code then be placed in the normal sql such as:
>insert into log (message, trace) values ('%m', '%throw')
>
>I remeber reading that custom conversions are fairly easy.  Anyone have a 
>pointer for me?
>
>Kevin

--
Ceki

SUICIDE BOMBING - A CRIME AGAINST HUMANITY
Sign the petition: http://www.petitiononline.com/1234567b
I am signatory number 22106. What is your number?


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>