On 2016-10-16, Nicholas Duane wrote: > By the way, what's the state of async appenders in log4net?
This is one of the things I'd love people to get involved in. We've got * a simple implementation inside the sample * https://issues.apache.org/jira/browse/LOG4NET-190 * https://issues.apache.org/jira/browse/LOG4NET-201 * https://issues.apache.org/jira/browse/LOG4NET-407 the later even made it into the 1.3 branch (that's now been abandoned). It would be good if anybody found the time to make it work inside the current trunk setup. So there are few implementations. They may share the problem mentioned here > http://stackoverflow.com/questions/36344822/log4net-appenders-onclose-doesnt-seem-to-work I haven't checked. > Seems like log4net should not only expose a startup routine the app > must call but also a shutdown routine, and indicate that it's > essential it gets called. Then log4net could shutdown the appenders > in the shutdown routine as opposed to relying on .NET's appdomain > shutdown logic. There are Shutdown methods in LogManager and LoggerManager. The patch Joe mentions that add Flush to certain appenders and to LogManager has been added to svn trunk and will be part of 2.0.6 (which will be the version of the next release). Stefan
