Hello, Internal error handling is one of the strong points of logback, the purported successor to log4j. Each logback component is attached to a context which maintains a publicly accessible list of internal errors. Search for StatusManager in logback documentation.
See also "Chapter 2 - Architecture" in the logback manual for further details: http://logback.qos.ch/manual/architecture.html I hope this helps, Stroboskop wrote:
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 it. 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...
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
