The book is great, I agree. Everyone using Log4j for any extended period of
time should have it.
It can be purchased here:
https://www.qos.ch/shop/products/clm_t.jsp
Ceki of course wrote the book, and I doubt he'd mind if anyone copies code
out of it. That's an interesting question by the way, maybe he'll comment.
Maybe his publisher would mind. :-)
Mike
-----Original Message-----
From: Larry Young [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2003 4:15 PM
To: Log4J Users List
Subject: RE: Enhancement Request
Steve,
I found it. It's described in the book "The Complete log4j
Manual" (ISBN: 2-9700369-0-8). It's an excellent book, get it if you can
actually find it (I got mine from an online book store in Colorado, it was
one of their last copies).
Anyhow, the class is called the RepeatFilter and it simply
compares the current output message to the previous one. You could also
enhance this to keep the last 'n' messages to compare against to avoid
repeats during a particular timeframe.
I'm not sure if this filter is part of the log4j distribution, you
might find it in the contrib section, or perhaps on the log4j website. I'd
put the code into this message, but I'd probably violate the heck out of
the publication copyright rules.
--- regards ---
Larry
At 12:16 PM 10/15/03, you wrote:
>Larry,
>
>I must confess that I started looking into log4j for the first time today,
>so I am not overly familiar with it. I browsed the classes looking at the
>Logger, and Appender classes (Layout didn't seem to make sense for this),
>and didn't see anything that met this need. I'll check out the Filters
>class and see what it can do. Thanx.
>
>-Regards,
> Steve
>
>-----Original Message-----
>From: Larry Young [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, October 15, 2003 2:04 PM
>To: Log4J Users List
>Subject: Re: Enhancement Request
>
>
>Steve,
>
> Why not do this with Filters? In fact, doesn't the SMTP appender
>have something like this already?
>
>--- regards ---
>Larry
>
>
>At 11:04 AM 10/15/03, you wrote:
> >To Log4J Team:
> >
> >I would like to recommend an enhancement to the Log4J toolkit. There are
> >applications in which it is desirable to put a ceiling on the number of
> >times any given message is reported. Parsers are an excellent example,
in
> >which warnings of the type "Token XXXXXX not found in record" really only
> >need to be reported once and not (possibly) thousands of times in a file
> >that obviously doesn't contain that token. I envision the configuration
> >file allowing one to set the Logger with a property of MAX_REPORTS which
> >allows one to place this ceiling on the number of times a message is
passed
> >to the Appender object. I recognize that this would slightly hurt the
> >performance as a comparison to a private integer variable would have to
be
> >made.
> >
> >Just a suggestion. Thanx for listening.
> >
> >-Regards,
> > Steve Widom
> >
> >Steve Widom
> >Advanced Technology Group Manager
> >AmerisourceBergen Specialty Group
> >Phone (972) 490-5551
> >www.amerisourcebergen.com
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
>
>--------------------------
>Larry Young
>The Dalmatian Group
>www.dalmatian.com
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------
Larry Young
The Dalmatian Group
www.dalmatian.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-------------------------------------------------------------------------------
This message and any included attachments are from Siemens Medical Solutions
USA, Inc. and are intended only for the addressee(s).
The information contained herein may include trade secrets or privileged or
otherwise confidential information. Unauthorized review, forwarding, printing,
copying, distributing, or using such information is strictly prohibited and may
be unlawful. If you received this message in error, or have reason to believe
you are not authorized to receive it, please promptly delete this message and
notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
