rm5248 commented on PR #135: URL: https://github.com/apache/logging-log4cxx/pull/135#issuecomment-1262992462
So after taking a look at this, what I was afraid of(not propagating the level to sub-loggers) is true. For example, if we have loggers `com` and `com.example` and we reconfigure to set the logger `com` to be `TRACE` for example, the `com.example` logger does not also get this level. This is assuming that the log configuration is coming from an XML file, although I think this would also be the case if you manually set the log levels. If you load an XML file with `com` set to `TRACE` at the beginning of execution, you will see the `com` and `com.example` messages output. This currently works fine in next_stable. I'll add a test for this feature soon, since it is something that I depend on often. There is a related issue, if you remove a logger from the configuration file and reload the file the logger will retain its currently set level. Unfortunately I don't really see an easy way of fixing this. We could reconfigure everything once we load the file, but that leads to a less than ideal situation of if a user is manually setting the log level they would now have to do an extra call at the end to have all of the loggers cache their new threshold level. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
