The EnhancedPatternLayout class already has options to suppress stacktrace.
See
http://logging.apache.org/log4j/companions/extras/apidocs/index.html?org/apache/log4j/rolling/RollingFileAppender.html
I'm still stumped on this issue and would welcome any thoughts or feedback.
In fact, I've tried to replicate my steps in my real application and
obtained similar results. Even reducing the number of loggers to just the
base package in my 'real' app results in empty files.
On Mon, Mar 25, 2013 at
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
