I should add that the LoggerConfig and Configuration was one of the first
things I worked on when I started working on 2.0. Things have changed since
then so it might possible to add a new LoggerConfig to an existing
configuration. I'd have to review it and remind myself of what the problems
http://logging.apache.org/log4j/2.x/manual/async.html
This URL describes that v2 has both async logger and async appender. What is
the suggested config for an embedded situation where I want low latency,
nothing fancy?
I've had do this in code since we don't own the cmd line: OSGi and
And if you can Javadoc things as you recall them, that much the better! :)
Gary
On Jul 23, 2013, at 11:23, Ralph Goers ralph.go...@dslextreme.com wrote:
I should add that the LoggerConfig and Configuration was one of the first
things I worked on when I started working on 2.0. Things have
Curt,
Without knowing your app env characteristics, I'd say that looks fine. The
ring buffer won't grow, so if you get bursts larger than 128 log events you
will see latency going up as logging will become IO bound when the ring buffer
is full.
Otherwise all seems reasonable.
Let me know
I feel apologetic for asking how to debug a v2 configuration but there's no
links off the v2 website. My env is embedded and I'm not getting any missing
classpath problems, I solved those. I am getting console output but none of my
FastRollingFile appenders are emitting their logs.
Some of
You did switch on AsyncLoggers using the context selector?
One reason you may not see FastFile output is if the buffer is not being
flushed.
AsyncLoggers auto-flush so this should not happen but since you're not seeing
output...
Several things to try:
* in the FastRollingFile appender config,
status=trace on the configuration element will enable debugging of the internal
components. It uses the StatusLogger, which is essentially just a special
Logger. You can add a listener to it do do what you want with the events. A
StatusConsoleListener is provided and is enabled by default when
