Guten Tag Alder Netw, am Donnerstag, 31. Juli 2014 um 03:15 schrieben Sie: > I did take a look at the code and it looks to me that the dispatch() is > dispatching to all appenders without waiting for the buffer being full. If > that is > the case, increase the buffer size won't make a difference in terms of > delaying > dispatching the events.
OK, I may have misunderstood the concept behind AsyncAppender. :-) Seems like you would need to implement some buffering on top of AsyncAppender to overcome the time needed for your appenders to become available. Could be possible by extending AsyncAppander and use the same buffering AsyncAppender alrerady does, but to override AsyncAppender::append and simply buffer everything until a recognized event that your needed appenders are available gets signaled. You would need a second thread like with the already used dispatcher which waits on that event and calls the base class AsyncAppender::append with the buffer contents and post it to the registered appenders. Once all your appenders are up, your own append method would directly pass log events through to the base class implementation. That way you could configure the size of your own buffer as needed to overcome the time your appenders need to be available, but wouldn't need to implement everything from scratch. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
