This is done through the getInstance() method, I believe.
On 5/4/07, James Stauffer <[EMAIL PROTECTED]> wrote:
#2 is commonly done for multi-threaded applications.
On 5/3/07, Edwin Lee <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> i have a multi-threaded application that needs to log to a single log
#2 is commonly done for multi-threaded applications.
On 5/3/07, Edwin Lee <[EMAIL PROTECTED]> wrote:
Hi all,
i have a multi-threaded application that needs to log to a single log file, and
am wondering which of the following would yield better performance:
1. Keeping several org.apache.log4j.L
Hi all,
i have a multi-threaded application that needs to log to a single log file, and
am wondering which of the following would yield better performance:
1. Keeping several org.apache.log4j.Logger instances, one for each thread,
configured using the same properties file (and hence all log to th
Don't know any off the top of my head, but keep in mind if you do
find any that AsyncAppender was considerably rewritten for log4j
1.2.13 (could be off on the version number, definitely in .14 the
current release) to eliminate a couple of different issues, so the
behavior should be signific
Hi,
Can anyone point me to any info regarding Stress Testing of Log4J
Appenders, especially Async Appender.
Thanks,
-Kamal.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
