Yes. But I was thinking there might be a section heading somewhere called
Location Information that specifically identifies each of the location patterns
and discusses the overhead of each. This is one area where I miss the C
preprocessor as the location stuff could have been hidden in a macro s
Ok, then to summarize my understanding for LOG4J2-219 the solution would be to:
* internally create a root logger if one isn't explicitly configured (like in
beta5)
* this default root logger would have level ERROR (like in beta5)
* this default root logger would not have any appenders configured
It occurs to me that given the way Log4j and Logback work they probably always
have a root logger that starts out not configured with an appender. I guess it
would make sense for us to do the same. I do think it makes sense to emit a
warning when no root logger is specified.
I agree with your
On the log4j user mailing list I encountered a user who had made a few wrong
turns, config-wise, and had trouble getting back on track.
One issue was that by default the File appender is buffered but does not flush.
So his log file stayed empty and he had trouble figuring out why.
Should we chan
