PropertyConfigurator.configure(filename); but never calling LogManager.resetConfiguration(); which meant if you removed a logging property from the configuration and reloaded it it carried on logging. It is a shame that the log4j APIs are so badly documented. LogManager being an example.
2 comments:
I've been using Log4J for about 6 years or so now, and still think it's probably the worst-documented library I've ever used.
I am there with you. The documentation goes round and round and gets nowhere. You would need to search, search, search, try, try and try to verify things.
Post a Comment