On Fri, 04 Nov 2005 09:35:31 -0800, Mark Womack wrote:
> Do you have any actual timing or profiling information that would lead
> you to suspect that log4j is causing the problem, or just anecdotal
> experience? There is nothing I can think of that changed so much in any
> of the recent log4j rele
Do you have any actual timing or profiling information that would lead you
to suspect that log4j is causing the problem, or just anecdotal experience?
There is nothing I can think of that changed so much in any of the recent
log4j releases to account for the level of degradation you are describing
On Fri, 04 Nov 2005 00:55:22 -0500, Frank W. Zammetti wrote:
> One thing that I'm curious about... are you actually instantiating a new
> Logger on each class instantiation (in the constructor I would guess)?
> If so, you might want to try making it a static member so the Logger
> instantiation
I'm using Log4J underneath JCL, and doing considerably more logging than
one entry per screen, and the performance of the one app I'm thinking of
in particular is stellar. And the hardware isn't anything grand and the
load is pretty significant, so I would say Log4J, in and of itself,
isn't th
In the most recent update to our system, I installed log4j 1.2.11. After
the update someone at our hosting facility finally noticed that the
application was taking a very long time to paint some screens. The
application was frequently painfully slow to begin with, but someone
latched on to log4j
