Return-Path: X-Original-To: apmail-logging-log4net-dev-archive@www.apache.org Delivered-To: apmail-logging-log4net-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BD0181045D for ; Tue, 30 Jul 2013 06:31:52 +0000 (UTC) Received: (qmail 49756 invoked by uid 500); 30 Jul 2013 06:31:52 -0000 Delivered-To: apmail-logging-log4net-dev-archive@logging.apache.org Received: (qmail 49719 invoked by uid 500); 30 Jul 2013 06:31:52 -0000 Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4NET Dev" List-Id: Delivered-To: mailing list log4net-dev@logging.apache.org Received: (qmail 49706 invoked by uid 99); 30 Jul 2013 06:31:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jul 2013 06:31:51 +0000 Date: Tue, 30 Jul 2013 06:31:51 +0000 (UTC) From: "Dominik Psenner (JIRA)" To: log4net-dev@logging.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (LOG4NET-385) I consistently have entries written to logs, but inconsistently get mail from the SmtpAppender. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LOG4NET-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723466#comment-13723466 ] Dominik Psenner edited comment on LOG4NET-385 at 7/30/13 6:30 AM: ------------------------------------------------------------------ Hi Tom, have you considered to bomb mails in your program and check if things go wrong there? Maybe your mails land in the spam folder of the recipient? Did you try if the same thing happens when using log4net 1.2.11? Have you enabled log4net's internal logging to see if there's something going wrong? However, if it sends emails once it should send them always unless there's something on the network/server side that blocks things. I, for instance, have noticed that often the smtp port is blocked in most companies so that their mail server does not get blacklisted by other servers. If your plan is to send emails when the application crashes, you should think about at least one fallback approach (i.e. a call to a REST service, web request, RPC, ..). Cheers was (Author: nachbarslumpi): Hi Tom, have you considered to bomb mails in your program and check if things go wrong there? Maybe your mails land in the spam folder of the recipient? Did you try if the same thing happens when using log4net 1.2.11? Have you enabled log4net's internal logging to see if there's something going wrong? However, if it sends emails once it should send them always unless there's something on the network/server side that blocks things. I, for instance, have noticed that often the smtp port is blocked in most companies so that their mail server does not get blacklisted by other servers. If your plan is to send emails when the application crashes, you should think about at least one fallback approach (i.e. a call to a REST service, web request, RPC, ..). Cheers > I consistently have entries written to logs, but inconsistently get mail from the SmtpAppender. > ------------------------------------------------------------------------------------------------ > > Key: LOG4NET-385 > URL: https://issues.apache.org/jira/browse/LOG4NET-385 > Project: Log4net > Issue Type: Bug > Components: Appenders > Affects Versions: 1.2.10 > Environment: Windows 7 > Reporter: Tom Jaeschke > Priority: Blocker > > I consistently have entries written to logs, but inconsistently get mail from the SmtpAppender. Is there any reason for the SmtpAppender to be dropping records? I get flaky results without regard to whether lossy is set to true or false. What may I do to troubleshoot? What are some sources for this pain point? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira