Thanks for not forgetting about it Mark.
Regards
Jeroen
-Original Message-
From: Mark Womack [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 20, 2002 6:29 PM
To: 'Log4J Users List'
Subject: RE: How are people using Chainsaw/LogFactor5?
I was going to point out SocketHubAppender, thank
hi all,
I have a problem in using AsyncAppender. Whenever I uses
RollingFileAppender which extends from FileAppender while inturn extends
from WriteAppender which extends from AsyncAppender, a large number of
threads are created and finally I got out of Memory Exception. My
properties file is a
WriterAppender and AsyncAppender both extends AppenderSkeleton, but are
otherwise unrelated. AsyncAppender can't be configured via
PropertyConfigurator. Your thread problem must stem from something else,
because no AsyncAppender will be created in your app unless you configure
its use via DOMConfi
i'm sorry but my last response was not entirely clear.
it *also* worked with 1.2.4 (which is why i mentioned that i did not change from
Category to Logger).
because of time constraints i did not push the testing very far. if you like, i will
try later today or
early next week to do a complete
At 14:46 19.06.2002 -0700, Klein, Scott @ TW wrote:
>I'm full of questions/comments today...
>
>Has anyone worried about the amount of resources (primarily mem space)
>attributed to Log4J to the extent that there was a need for a
>"StaticHierarchy" whereby, if a user requests a Logger that does n
>Logger x1 = Logger.getLogger("x");
>Logger x2 = Logger.getLogger("x");
>
>Both x1 and x2 reference the exact same object.
Of course, but you lose the class level granularity for configurations.
Which is exactly what I would like to keep, and in order to do so you must
create loggers by class.
T
At 13:04 21.06.2002 -0700, you wrote:
> >Even if the saving in the memory footprint were important (which they are
>not!)
>
>Why is saving memory not important?
I did not say saving memory was not important!
I mistyped "savings" as "saving" which apparently changed the meaning
of the sentence. W
Howdy,
>Why is saving memory not important?
Saving memory is important. However, like Ceki said (I've verified this
using a profiler for our system), the Logger instances (even at 1 for
each class) take so much less memory than your application classes, that
their memory footprint is insignific
Hi List,
I´m using the Loj4J at a big project here in the Brazil, and I would like
that anybody pass me a sample code example in the Internet, where I can look
it, diferent of the examples that come with the jakarta-log4j package. I
would like a real sample code example.
Please help me.
Fabi
Stopping root category/logger from logging child categories/loggers for
DEBUG messages only.
My question is how to stop DEBUG logging message from being visible above
certain logger.
Let say, loggers are
a DEBUG to be directed into a common-log
a.b DEBUG
10 matches
Mail list logo
