Re: Log4J - Downsides?

["Michael S Young" <msyoung@MetLife.com>]

The only "problem" I've noticed with log4j is...

If you reload the config file (through PropertyConfigurator.configure() or
configureAndWatch() API), a _small_ number events might get lost as the
appenders are closed and reopened.  Log4j will write an error to stderr
stating that it couldn't send the event(s) to the appender-so at least you
know it is happening.
In exchange for being able to dynamically configure the logging behavior
with the config file, I don't see this as a major problem.

If you can't afford to lose any events, you can request a smaller-scale
change by calling Category.setPriority().
I haven't seen this API lose events yet.

-Mike

P.S. - I happened to be using the RollingFileAppender, but I assume the
problem would occur with any appender.





"Paul Rogers" <ironstack2000@hotmail.com> on 04/12/2002 11:52:18 AM

To:    ajug-members@www.ajug.org
cc:
Subject:    Log4J - Downsides?


Going to pitch using log4j to my company next week.
I've tried it out within some of the existing code and seems to be great.

However, has anyone seen any problems using this API?
Things like performance issues, security...

This will used with servlets, and other backend code, running on JRun 2.3.2


My company is open-source unfriendly to start with, so it will be an uphill
fight..

_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com