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
Hi,
c:\Branches\main\cb\ExternalLibs\include\log4cxx\helpers
\appenderattachableimpl.h(106) : warning C4250:
'log4cxx::helpers::AppenderAttachableImpl' : inherits
'log4cxx::helpers::ObjectImpl::log4cxx::helpers::ObjectImpl::addRef'
v ia dominance
c:\Branches\main\cb\ExternalLibs\includ
Curt Arnold wrote:
On May 10, 2005, at 1:06 PM, Kevin Tew wrote:
I'm getting tons of these warnings for every log4cxx class
Any Ideas?
c:\Branches\main\cb\ExternalLibs\include\log4cxx\helpers
\appenderattachableimpl.h(106) : warning C4250:
'log4cxx::helpers::AppenderAttachableImpl' : inherits
On May 10, 2005, at 1:06 PM, Kevin Tew wrote:
I'm getting tons of these warnings for every log4cxx class
Any Ideas?
c:\Branches\main\cb\ExternalLibs\include\log4cxx\helpers
\appenderattachableimpl.h(106) : warning C4250:
'log4cxx::helpers::AppenderAttachableImpl' : inherits
'log4cxx::helpers::
I'm getting tons of these warnings for every log4cxx class
Any Ideas?
c:\Branches\main\cb\ExternalLibs\include\log4cxx\helpers\appenderattachableimpl.h(106)
: warning C4250: 'log4cxx::helpers::AppenderAttachableImpl' : inherits
'log4cxx::helpers::ObjectImpl::log4cxx::helpers::ObjectImpl::addRef'
Viet Pham wrote:
I am from Market Development Engineering department at Sun Microsystems.
I have some questions about log4j Solaris 10 supports. Could you please
point me to the right person? Thanks.
I'm going to go out on a limb here and suggest that the right place to
get answers about log
Hi all,
I am from Market Development Engineering department at Sun Microsystems.
I have some questions about log4j Solaris 10 supports. Could you please
point me to the right person? Thanks.
Christophe de Vienne wrote:
CriticalSection initialise a recursive mutex. For most use it's OK,
but some people may need a simple one for performances issue, and
there is a third one which can report errors.
What I propose is to give the type of mutex we need to the
constructor, with a default t
Michaël CATANZARITI wrote:
Hi,
Christophe de Vienne wrote:
Hi,
I'm currently working on the threading wrappers, mainly hidding the
implementation details dependant from the thread system we use.
I have a few questions :
1) In Thread::~Thread(), the join is done directly instead of using
T
Hi,
Christophe de Vienne wrote:
Hi,
I'm currently working on the threading wrappers, mainly hidding the
implementation details dependant from the thread system we use.
I have a few questions :
1) In Thread::~Thread(), the join is done directly instead of using
Thread::join, which make
Hi,
I'm currently working on the threading wrappers, mainly hidding the
implementation details dependant from the thread system we use.
I have a few questions :
1) In Thread::~Thread(), the join is done directly instead of using
Thread::join, which make code duplication. Is there a parti
16 matches
Mail list logo