logs are tracked in some way and the performace is not
affected.
Is it feasible?
Subject: Re: Problems with FileoverAppender
From: ralph.go...@dslextreme.com
Date: Tue, 26 Mar 2013 10:32:24 -0700
To: log4j-user@logging.apache.org
I've been doing some work on the SocketAppender, which
the buffer gets full and the I/O takes place, the entire content of the
buffer is written on the alternative appender, instead of only the last
message. This will guarantee that all logs are tracked in some way and the
performace is not affected.
Is it feasible?
Subject: Re: Problems
, instead of only the last message. This
will guarantee that all logs are tracked in some way and the performace is not
affected.
Is it feasible?
Subject: Re: Problems with FileoverAppender
From: ralph.go...@dslextreme.com
Date: Tue, 26 Mar 2013 10:32:24 -0700
To: log4j-user@logging.apache.org
Hi all,
I'm writing an application where I want to log to a Syslog server. I'm doing it
using a FailoverAppender, so when the Syslog server is down I can log to a
local file. I'm using Log4j 2.0beta4.
Here is my log4j2.xml configuration file:
configuration
appenders
RollingFile
I've been doing some work on the SocketAppender, which is the base for the
SyslogAppender. The SocketAppender is not flushing the OutputStream on every
send. From what I can tell this is causing the data to be buffered and the
exception only gets thrown when the buffer gets full and actual I/O
