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
On Wed, Jul 30, 2014 at 12:05 AM, Thorsten Schöning
wrote:
> Guten Tag Alder Netw,
> am Mittwoch, 30. Juli 2014 um 01:06 schrieben Sie:
>
> > How is the log4cxx buffering works exactly?
>
> Just look at AsyncAppender, log4cxx is Open Source. I already
> described how it is working.
>
> > say if y
Guten Tag Alder Netw,
am Mittwoch, 30. Juli 2014 um 01:06 schrieben Sie:
> How is the log4cxx buffering works exactly?
Just look at AsyncAppender, log4cxx is Open Source. I already
described how it is working.
> say if you specify a
> large buffer size, is the first log message sent out after th
Thanks Thorsten for the reply. Yes, it is a hard problem. On one side,
users would
like not to miss any logs after the system comes up; On the other hand,
some external
syslog servers needs some extra handling to resolve its DNS names for
instance (we
choose to do dns name conversion ourselves beca
Guten Tag Alder Netw,
am Dienstag, 29. Juli 2014 um 00:44 schrieben Sie:
> Say, if we create a log4cxx::AsyncAppender(), and add an appender A
> which is ready to it via addAppender() at time t0, and when another appender
> B is ready and is added to it at a later time t1. Would the
> messages b
Say, if we create a log4cxx::AsyncAppender(), and add an appender A
which is ready to it via addAppender() at time t0, and when another
appender
B is ready and is added to it at a later time t1. Would the messages
between t0 and t1 be sent to B after it's up? If not the the app needs to
buffer the
