pplication
closes, which forces the last logs to complete before the application
completely closes.
Thanks.
-Original Message-
From: Curt Arnold [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 10, 2007 3:58 PM
To: Log4J Users List
Subject: Re: AsyncAppender Issue
>
> Has anyone else
On Apr 10, 2007, at 4:01 PM, Kamal Ahmed wrote:
Maybe , Async Appender can be re written using
java.util.concurrent.LinkedBlockingQueue
Just a suggestion
-Kamal.
LinkedBlockingQueue was introduced in JDK 1.5. log4j 1.2 must run on
older JVM's and alternative JVM's that do not suppor
Maybe , Async Appender can be re written using
java.util.concurrent.LinkedBlockingQueue
Just a suggestion
-Kamal.
-Original Message-
From: Curt Arnold [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 10, 2007 4:58 PM
To: Log4J Users List
Subject: Re: AsyncAppender Issue
>
&g
Has anyone else experienced this type of behavior with the
AsyncAppender?
Thanks.
Nope. You should pack up your test case and file a bug report to see
if we can figure out what is going on. If you can identify the
problem and propose a patch even better.
---
Original Message-
From: James Stauffer [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 10, 2007 2:36 PM
To: Log4J Users List
Subject: Re: AsyncAppender Issue
How are you configuring AsyncAppender. I think it has an option that
throws away logs when the buffer is full.
On 4/10/07, Luedeck
How are you configuring AsyncAppender. I think it has an option that
throws away logs when the buffer is full.
On 4/10/07, Luedecke, Michael J <[EMAIL PROTECTED]> wrote:
I'm losing logs when I use the AsyncAppender for some reason. This loss
of logs occurs whether I'm using a custom appender o
I'm losing logs when I use the AsyncAppender for some reason. This loss
of logs occurs whether I'm using a custom appender or out-of-the-box
appender (i.e. FileAppender).
I have not noticed this problem when I send a string in the log method
call. It only seems to happen when I pass an object
