I can, yes.
Nick
On Jul 26, 2013, at 5:20 PM, Gary Gregory wrote:
> The approach currently implemented sounds good to me.
>
> Nick, can you document the appender's behavior to avoid further confusion?
>
> Thank you,
> Gary
>
> On Jul 26, 2013, at 14:32, Nick Williams
> wrote:
>
>> Yes, thi
The approach currently implemented sounds good to me.
Nick, can you document the appender's behavior to avoid further confusion?
Thank you,
Gary
On Jul 26, 2013, at 14:32, Nick Williams wrote:
> Yes, this is the intended behavior, and a false-positive on the part of the
> leak detection.
>
>
Yes, this is the intended behavior, and a false-positive on the part of the
leak detection.
If the JDBCAppender has to open and close a connection and prepare the same
statement for each logging event (even if it just has to borrow a connection
from a pool and prepare the same statement for eac
Hello,
I'm working on using the JDBCAppender and am seeing a leaked connection.
I'm using Glassfish 3.1 with Jersey and Oracle using a JNDI connection for
log4j.
In my test app just doing a single log will reach the database fine, but
then I get the leaked
connection warning from Glassfish for the
