Jacob L. Anawalt wrote:
I'm going to give the LevelRangeFilter object a go via filter statements
in an XML config.
This appears to be a very workable solution for my needs. I expect that the
Threshold option to an Appender is slightly more efficient, but I am not worried
about it.
Thank you
Curt Arnold wrote:
I think the trailing semi-colon after WARN is messing you up.
Thank you for pointing that out. I will watch for that in the future.
Unfortunately it turned out to be more than this. The full app I am testing did
not have the semi-colon and neither did the XML config I tried
On Feb 29, 2008, at 5:10 PM, Jacob L. Anawalt wrote:
Jacob L. Anawalt wrote:
I am getting info and debug messages in my system logs.
I have purchased the log4j manual and it looks like I have the
appender threshold settings correct.
Here is the output of the attached program and configur
Jacob L. Anawalt wrote:
I am getting info and debug messages in my system logs.
I have purchased the log4j manual and it looks like I have the appender
threshold settings correct.
Here is the output of the attached program and configuration file.
2008-02-29 23:07:12 DEBUG root - 1
2008-02-
Hello,
I want errors >= WARN to go to syslog and nothing else that happens to get
inserted into the log stream so I attempted to use the Threshold option in
AppenderSkeleton (which my docs show SyslogAppender inheriting from) mentioned
in FAQ 2.9 [1].
#PropertyConfigurator file
log4j.appende
