[jira] [Created] (LOG4NET-516) Slow email servers can cause SmtpAppender to slow down any system using it
john weidman created LOG4NET-516: Summary: Slow email servers can cause SmtpAppender to slow down any system using it Key: LOG4NET-516 URL: https://issues.apache.org/jira/browse/LOG4NET-516 Project: Log4net Issue Type: Improvement Components: Appenders Affects Versions: 1.2.15 Environment: Windows 7 & 10 Reporter: john weidman Fix For: 1.2.15 When using log4net with an SmtpAppender if the email server that the messages are going to is under an excessive load and the messages back up all of the Log4Net logging slows down and makes the system unusable. It seems like exposing the timeout value on the SmtpClient as a configurable option would allow code to continue, even if it does drop an email request. Otherwise the logging system can bring the system to a standstill. The default Timeout for SmtpClient is 100 sec. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not
[ https://issues.apache.org/jira/browse/LOG4NET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304343#comment-15304343 ] ASF GitHub Bot commented on LOG4NET-467: Github user chlowell commented on the pull request: https://github.com/apache/log4net/pull/16#issuecomment-222199688 I have another branch on my fork (`dotnetcore-rc2`) which builds with RC2 tools, and has some improvements over the code here. A few tests are broken due to executing with NUnitLite. Once the NUnit runner is updated for RC2 (nunit/nunit#1371), I'll open a new PR. > Is .NET Core, will be supported in the near future, or not > -- > > Key: LOG4NET-467 > URL: https://issues.apache.org/jira/browse/LOG4NET-467 > Project: Log4net > Issue Type: New Feature > Components: Core >Affects Versions: 1.2.13 >Reporter: san kan > Labels: features > > As you know, ms is moving heavily toward .Net core: > https://github.com/dotnet/core > so, is there a road map for making a version that supports it? > and i noticed that log4net, has not been updated for 2 years. > so is it maintained, or being forgotten? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] log4net pull request: [WIP] (LOG4NET-467) .NET Core support
Github user chlowell commented on the pull request: https://github.com/apache/log4net/pull/16#issuecomment-222199688 I have another branch on my fork (`dotnetcore-rc2`) which builds with RC2 tools, and has some improvements over the code here. A few tests are broken due to executing with NUnitLite. Once the NUnit runner is updated for RC2 (nunit/nunit#1371), I'll open a new PR. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (LOG4NET-415) RemoteSyslogAppender may block for ARP resolution + Improvement Strict RFC3164
[ https://issues.apache.org/jira/browse/LOG4NET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304149#comment-15304149 ] Jose Luis Pedrosa commented on LOG4NET-415: --- Hi Is there any way to get this patch applied to log4net? should I do a PR or something? would it help? Rgds JL > RemoteSyslogAppender may block for ARP resolution + Improvement Strict RFC3164 > -- > > Key: LOG4NET-415 > URL: https://issues.apache.org/jira/browse/LOG4NET-415 > Project: Log4net > Issue Type: Bug > Components: Appenders >Affects Versions: 1.2.13 > Environment: Any Windows environment >Reporter: Jose Luis Pedrosa > Labels: RemoteSyslogAppender > Attachments: LOG4NET-415.patch, MessageLostTest.cs, > MessageLostTest.cs, MessageLostTestAsync.cs, RemoteSyslogNonBlockingV3.patch, > RemoteSyslogNonBlockingv2.patch > > > Sending UDP packages may block for some time in specific circumstances: > 1) Next hop in network level 3 can't be resolved by ARP. > 2) Datagram size exceeds FastSendDatagramThreshold configured size. > When sending packets bigger than FastSendDatagramThreshold, the OS waits > until the packet is actually sent, if the If the syslog (or the next hop to > reach the syslog) is in the same VLAN/Subnet the OS tries to resolve by ARP > the Ip of the configured syslog, this may take up to 3 seconds, slowing down > the whole application, which in some cases can lead to outages (timeouts, DB > locks...). > Also the fact that each carriage return generates the headers of the packet > again, that can lead to a significant overhead in some scenarios, for > instance when loggign HTTP requests to a remote syslog, every header will go > in a different message. Also some logging may require characters that are now > skipped in patch: https://issues.apache.org/jira/browse/LOG4NET-370 > I'm adding a patch that > 1) Moves the use of UDPClient to Non blocking sockets, which eliminates the > blocking. > 2) Adds a configuration field to decide if you want Strict RFC Behaviour or > not (with default Strict). > Please your feedback, thanks in advance > Jose Luis -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not
[ https://issues.apache.org/jira/browse/LOG4NET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303822#comment-15303822 ] ASF GitHub Bot commented on LOG4NET-467: Github user chester89 commented on the pull request: https://github.com/apache/log4net/pull/16#issuecomment-222102483 @chlowell any updates on this? > Is .NET Core, will be supported in the near future, or not > -- > > Key: LOG4NET-467 > URL: https://issues.apache.org/jira/browse/LOG4NET-467 > Project: Log4net > Issue Type: New Feature > Components: Core >Affects Versions: 1.2.13 >Reporter: san kan > Labels: features > > As you know, ms is moving heavily toward .Net core: > https://github.com/dotnet/core > so, is there a road map for making a version that supports it? > and i noticed that log4net, has not been updated for 2 years. > so is it maintained, or being forgotten? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] log4net pull request: [WIP] (LOG4NET-467) .NET Core support
Github user chester89 commented on the pull request: https://github.com/apache/log4net/pull/16#issuecomment-222102483 @chlowell any updates on this? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
