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 and have not seen it myself.
If you switch back to version 1.2.9, does your problem go away? -Mark On 11/3/05, Michael A Chase <[EMAIL PROTECTED]> wrote: > > 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 as something that had changed recently. > > In production, the application is calling Logger.getLogger() once for most > class instantiations (5-10 per screen) and logger.warn() once per screen. > There is only one appender which uses DailyRollingFileAppender. > > Has anyone seen log4j cause a noticeable performance degradation when > writing one log entry per screen displayed? > > -- > Mac :}) > Give a hobbit a fish and he eats fish for a day. > Give a hobbit a ring and he eats fish for an age. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
