Ok,
I switched over to JDBC logging to my database a couple days ago. Setup
the tables in the DB, granted permissions to the DB user, and it all works
great...except for a lag time in the login process now. It is taking
about 20 seconds to login. The login process is quite simple takes the
in
I typically fall back on looking at the input files for the test suite
when I need an example, the files in tests/input/filters may help.
I had made a very primitive start on an XML schema for configuration
file that was intended eventually to provide the documentation for the
configuration fil
http://wiki.apache.org/logging-log4j/LogByLevel
That link will show you an example configuration file the uses a
Filter. You'd have to replace the LevelMatchFilter with your own class
of course, but this link's information should get you started.
cheers,
Paul
Steve Kuo wrote:
Thanks for the qui
Thanks for the quick reply.
Writing the actual filter seems pretty
straightforward. How would I go about specifying or
plugging in a Filter implementation? Unfortunately the
short intro to log4j by Ceki Gülcü makes no mention of
filters or using an XML file to specify the config.
Thanks, Steve
-
This is quite easy if you code yourself a little Filter class. An
appender can be given a Filter, so create a Filter impl that takes the
event, works out whether it's the type that's been trapped before, and
return Filter.DENY if you don't want to see it.
The class should only be a handful of
We're using a third party product (JGroups) which
instead of logging an error just once, keeps logging
the same error repeatedly. This is annoying as it
fills up the log file.
Is there a way to configure log4j to only log an error
so many times (for a particular logger instance)?
After the maximum
There is another way to get location info into Chainsaw V2 from 1.2.9:
Generate events using a FileAppender and specify line/file/etc in the
patternlayout. This file must be accessible to Chainsaw as a URL (http or file
url).
You can then use a LogFilePatternReceiver in Chainsaw to parse (and
GERODOLLE Anne RD-MAPS-GRE wrote:
Hi Curt,
following your answer I have downloaded logging-chainsaw, read the install instructions. It told me to use log4g 1.3 . Thus, I downloaded log4j1.3alpha6.tar.gz and tried to build it.
After some progress, I am still unsuccessfull, and read in a post you d
Hi Curt,
following your answer I have downloaded logging-chainsaw, read the install
instructions. It told me to use log4g 1.3 . Thus, I downloaded
log4j1.3alpha6.tar.gz and tried to build it.
After some progress, I am still unsuccessfull, and read in a post you did that
the alpha version is on
On Fri, 29 Apr 2005, Ceki Gülcü wrote:
|
| Log4j developers are proud to announce the availability of log4j
| version 1.2.10. This version adds native support for SLF4J, along with
| a minor bug fix. The Simple Logging Facade for Java or (SLF4J) is
| intended to serve as a simple facade for variou
10 matches
Mail list logo
