logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stroboskop <gnubeu...@web.de>
Subject How to handle log4j's internal exceptions
Date Mon, 11 Jun 2007 16:51:52 GMT

OK, here's my problem:
i want to know when _log4j_ is having a problem.

For example: imagine using a FileAppender pointing to a directory on the
network - sometimes you don't have write access rights and sometimes the
directory's just not available. Anyway your chances are good that regular
logging wont work at all.
So i want to be notified, when log4j catches an exception.

Since log4j's internal problems are logged using LogLog, i might need to
somehow implement/overload the internal logging. How do do that?

Originally i thought, i'd just need to register an exception handler with
log4j, but there doesn't seem to be such a thing. Or at least i didn't find

I know only the most basic things about log4j, so maybe it's easy. But i
looked at the wiki, faq's and the API and did't find anything that helped...

View this message in context: http://www.nabble.com/How-to-handle-log4j%27s-internal-exceptions-tf3902661.html#a11064210
Sent from the Log4j - Users mailing list archive at Nabble.com.

To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org

View raw message