Log4j will never throw an exception through its printing methods (Logger.debug(), Logger.info(), ...). However, it will print a warning message on the console. That is the default behavior which can be customized using error handlers.
It is entirely possible for the Java io API to silently ignore the fact that the file is gone. That is a Java issue and log4j cannot do anything about it.
At 10:29 AM 8/29/2003 +1000, Raveendranath, Rohith (LNG - AUS) wrote:
whetrher logging activity is critcal for any application will be the guiding factor to decide whether the application should crash i case of logging failure.
Morover what iam asking is should't a warning be thrown on the console saying that the logging cannot be proceeded or so
-- Ceki For log4j documentation consider "The complete log4j manual" ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
