Hi Thomas,
Thanks for the information.
But WRT the question 2 what I meant was how does Log4J internally scale when there is
low volume verses high volume and I know that it is thread safe. Is there some
external configuration on how log4J scales or is it handled automatically?
Thanks
Rav
| Hi,
|
| I am fairly new to Log4J and I have the following questions.
|
| By default if I use the ConsoleAppender or any other appender other
| than AysncAppender, they are all synchronous. Correct?
Yes.
| 1. To use the appender in an aysnc way, I have to extend it from the
| As
| Is it true?
Yes. If you consult the javadoc for org.apache.log4j.AsyncAppender in log4j,
you will find the statement:
"Important note: The AsyncAppender can only be script configured using the
DOMConfigurator."
Hope this helps.
--
Thomas
*
The AsyncAppender does not wait for the buffer to be full but why should
that be labeled as a problem?
At 11:44 12.09.2002 +0200, you wrote:
>Hello,
>
>I'm having problems when using an AsyncAppender, it doesn't seem to wait
>for the buffer to be full, but writes the logs one by one.
>My progra
You can try to reproduce the problem by not using AsyncAppender. If
you still get an out of memory error you know who to blame.
At 18:21 09.07.2002 -0400, you wrote:
>I have a large web application that has just begun failing with a gnarly
>bug.
>The AsyncAppender dispatcher thread dies, which c
In your TracerLogger getCategory() method, you have:
cat.addAppender( new AsyncAppender());
That (obviously) creates a new appender for -every- class. Try configuring once and
putting the appender on the root category. Obviously you don't need a different
appender for every c
Nope
It's for letting a second thread handle the actual logging. This means that
the thread initiating the logging will gain control immediately after
submitting the entry, and the logging-thread (which is a low-priority daemon
thread) will only send the entry to the sink when the application thr
Hi Michiel,
The benefit of the AsyncAppender is not that logging
runs faster (ie log messages get written to disk faster),
but that code which *calls* log methods runs faster,
because it does not wait for the logged message to
be written.
In order to prove this, what you need is a very slow Appe
Michiel,
The usefulness or lack thereof of AsyncAppender is not dependent on the OS. The new
JVMs do file buffering on all platforms. Don't confuse buffering of the file write
operation with what AsyncAppender does.
File buffering let you write large chunks to disk instead of writing small ch
Ceki Gülcü <[EMAIL PROTECTED]> wrote:
> Michiel,
>
> What kind of testing are you doing? What do you mean by logging gets
> faster? With respect to what? Cheers, Ceki
A loop with in it one logging statement, and sometimes a delay. It get
faster per logging then without a delay. That's the idea
Michiel,
What kind of testing are you doing? What do you mean by logging gets faster? With
respect to what? Cheers, Ceki
At 10:59 12.02.2001 +0100, you wrote:
>I did a little research if using the AsyncAppender would make
>sense. So, I made a little program with delays in it etc, as is
>sugg
11 matches
Mail list logo
