Comments on: A better SMTPAppender http://blog.cherouvim.com/a-better-smtpappender/ software engineering for beginners Mon, 06 Sep 2010 20:44:19 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: bayilik http://blog.cherouvim.com/a-better-smtpappender/comment-page-1/#comment-1440 bayilik Sun, 05 Sep 2010 13:20:20 +0000 http://blog.cherouvim.com/?p=98#comment-1440 We entered to a program as Bayilik Franchise Program. This post made help us for improve our software. We will send our software for your recommend. We entered to a program as Bayilik Franchise Program. This post made help us for improve our software. We will send our software for your recommend.

]]> By: Ellie Perrett http://blog.cherouvim.com/a-better-smtpappender/comment-page-1/#comment-1355 Ellie Perrett Fri, 07 May 2010 15:34:48 +0000 http://blog.cherouvim.com/?p=98#comment-1355 Informativer Artikel, vielen Dank. Informativer Artikel, vielen Dank.

]]> By: cherouvim http://blog.cherouvim.com/a-better-smtpappender/comment-page-1/#comment-1174 cherouvim Thu, 20 Aug 2009 15:15:43 +0000 http://blog.cherouvim.com/?p=98#comment-1174 Yes that is correct. My implementation is very simple and may ignore important errors after the limit per minutes is up. Possible improvements could include caching all errors and sending them in one mail or comparing them somehow (pattern matching) to make sure that it does not ignore different errors even when the threshold has been exceeded. Of course, if the production server starts sending errors you ought to SSH and view the log4j logs yourself :) Yes that is correct. My implementation is very simple and may ignore important errors after the limit per minutes is up. Possible improvements could include caching all errors and sending them in one mail or comparing them somehow (pattern matching) to make sure that it does not ignore different errors even when the threshold has been exceeded.

Of course, if the production server starts sending errors you ought to SSH and view the log4j logs yourself :)

]]> By: ifi http://blog.cherouvim.com/a-better-smtpappender/comment-page-1/#comment-1173 ifi Thu, 20 Aug 2009 14:52:33 +0000 http://blog.cherouvim.com/?p=98#comment-1173 Neat post. I'm struggling with the same problem. I did something like you did but ran into the following problem. Example: Limit it to say 3 emails every 10 minutes. Let's say you get all 3 emails in the first few seconds. You fix the errors. Then you get another error at minute 9. But your quota is up, so it doesn't send an email. Then the app stops logging b/c there is nothing to log for now. You will never be notified of the error from minute 9, right? I think it's better to use a timer to check if an errors have been cached and then send an email. What do you think? Neat post. I’m struggling with the same problem. I did something like you did but ran into the following problem.

Example: Limit it to say 3 emails every 10 minutes. Let’s say you get all 3 emails in the first few seconds. You fix the errors. Then you get another error at minute 9. But your quota is up, so it doesn’t send an email. Then the app stops logging b/c there is nothing to log for now. You will never be notified of the error from minute 9, right?

I think it’s better to use a timer to check if an errors have been cached and then send an email. What do you think?

]]>