gmane.comp.apache.logging.log4net.devel

[jira] Created: (LOG4NET-179) Log file does not get created by release version of App.exe

Shetal Shah (JIRA — 2008-10-06T18:49:44

Log file does not get created by release version of App.exe ----------------------------------------------------------- Key: LOG4NET-179 URL: https://issues.apache.org/jira/browse/LOG4NET-179 Project: Log4net Issue Type: Test Affects Versions: 1.2.10 Environment: Visual Studio 2005, language C#, OS Windows XP Professional Reporter: Shetal Shah I have a windows application that uses log4net. My app.config section has

When I build my exe in debug mode and run it, it works fine and log4net.Repository.ILoggerRepository RootRep; RootRep = log4net.LogManager.GetRepository(); RootRep is configured and has one appender. Now, same code but when I compile the exe in release mode, it does not create log file. RootRep is not configured and it has 0 appender. I am not sure what is different between debug and release exe. Any help is greatly appriciated. Thanks Shetal Shah

[jira] Created: (LOG4NET-178) Log4Net stops logging after appdomain recycle of aps.net2.0 application

Richard Nijkamp (JIRA — 2008-10-06T08:37:45

Log4Net stops logging after appdomain recycle of aps.net2.0 application ----------------------------------------------------------------------- Key: LOG4NET-178 URL: https://issues.apache.org/jira/browse/LOG4NET-178 Project: Log4net Issue Type: Bug Components: Appenders Affects Versions: 1.2.10 Environment: Windows server 2003 Reporter: Richard Nijkamp Dear sir/madam, We are using Log4Net 1.2.10. We encounter the problem that Log4net doesn't continue logging after an event that triggers an appdomain recycle/restart. In the global.asax we start the logging with: private static readonly ILog log = LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType); Logging works flawless when the application is started for the first time. After sometime it might occur that the appdomain gets recycled due to inactivity of the web application. We use the following code in Application_end(): log.Info("*** Application end ***"); log4net.LogManager.Shutdown(); After this function the application gets restarted and the Application_start() method executes and writes new lines to the log. The problem is that the log4net doesn't write the new lines after the restart. Could you explain why log4net might stop working after an appdomain restart of an asp.net2.0 web application? If I want log4net to work properly again I need to restart IIS manually. Looking forward to your reply. Best regards, Richard Nijkamp

[jira] Created: (LOG4NET-177) How to get the pattern convert string form layout?

anvy0314 (JIRA — 2008-10-06T08:11:44

How to get the pattern convert string form layout? -------------------------------------------------- Key: LOG4NET-177 URL: https://issues.apache.org/jira/browse/LOG4NET-177 Project: Log4net Issue Type: Test Affects Versions: 1.2.10 Reporter: anvy0314 Hi, I want to get the whole string after pattern format, how to do it, thanks! Like this string "2008-10-06 15:50:45,875 [192.168.7.103] DEBUG PingTestLogger..." before write to the log file.

[jira] Created: (LOG4NET-176) Buildable with VS 2008 and .NET FW 3.5

Nicklas Norling (JIRA — 2008-10-04T13:19:44

Buildable with VS 2008 and .NET FW 3.5 -------------------------------------- Key: LOG4NET-176 URL: https://issues.apache.org/jira/browse/LOG4NET-176 Project: Log4net Issue Type: New Feature Components: Builds Environment: Windows, log4net trunk, vs 2008 .net 3.5 Reporter: Nicklas Norling Priority: Minor Fix For: v.Next Providing a patch for the changes I'm using when compiling log4net locally using vs2008 and .net 3.5. The patch is created against trunk < at > 701632. It adds project and solution files for vs 2008, adds compilation symbol NET_3_5 which is then added to all conditional compilation statements that have NET_2_0 today. Also the AssemblyInfo.cs has a .NET 3.5 section added. Since the project files have to be manually updated when new files are added to trunk I would appretiate it if this patch (or one with similar functions) where added to trunk.

Configuration system enhancement

François Dumont — 2008-10-01T19:34:28

Hi We are using log4net through out all our applications and are very happy with it. I would like to know however if you ever considered enhancing the configuration system. I would be especially interested in being able to fully initialize log4net programmatically. All the sample I have been able to find are always using an xml description but there are parameters we need to pass to a special appender we have develop that simply cannot be serialized. Bests François Dumont

Appender to run at a Schedule Time

HemantJPatel — 2008-09-30T15:29:53

Hi, I need to run the smtp appender at a specified interval of time. Any ideas how I can do this to that the appender will run at specific intervals and send all the buffered messages. Any pointers will be helpful. Thanks in advance. Thanks, Hemant

[jira] Created: (LOG4NET-175) RollingFileAppender generates unexpected filename and/or causes IIS to hang

Devan Iyer (JIRA — 2008-09-29T23:10:45

RollingFileAppender generates unexpected filename and/or causes IIS to hang --------------------------------------------------------------------------- Key: LOG4NET-175 URL: https://issues.apache.org/jira/browse/LOG4NET-175 Project: Log4net Issue Type: Bug Components: Appenders Affects Versions: 1.2.9 Environment: win32 Reporter: Devan Iyer We are using rolling file appender in an IIS managed C# application. Our log4Net deployment is configured with the following options specified in basic.xml: . The file pattern for our log file name is "abc_%date{yyyyMMdd_HHmmss}_%processid_.log". We have observed in our production environment that occasionally filenames would be created with patterns like "abc_%date{yyyyMMdd_HHmmss}_%processid_.log.1", "abc_%date{yyyyMMdd_HHmmss}_%processid_.log.1.2", "abc_%date{yyyyMMdd_HHmmss}_%processid_.log.1.2.3", etc. We have observed filenames with the dot+sequential numbers pattern after the .log to be anything from ".1" to ".220". This is one of two unexpected behaviours observed. The second unexpected behaviour seems to a special case of the first that occasionally causes IIS to hang (100% CPU consumption). An analysis of several crash dumps taken at the time of the hang indicated that RollingFileAppender had in memory a filename of the same pattern as above but with the number of characters [base filename pattern]+[recurring extension pattern] exceeding 255 characters. It is very likely that an attempt to create a file by such name on NTFS would throw exceptions at various levels - managed and native - and hence the file itself is never created. To the best of our knowledge, there were no events to trigger the filename to be rolled. As indicated in the configuration options, we are using RollingStyle of "Once". (The log file content is minimal at the time the symptoms occur - total file size is about 2K - and the times of occurrence are totally non related). We have been unable to capture the workflow leading up to the symptoms above due to the high number of users and document types in our production environment. The permissions on the logging folder are static. However, we have found a simple workflow in our lab environment, using permissions, that produce similar symptoms. This workflow is: - Right click on the logging folder and select "Properties" - Under the "Security" tab ensure that IIS_WPG group doesn't have write access to the logging folder. - Restart IIS - Launch our application and view a document. Check the logging folder to make sure that a logfile is not created. - View a few more documents - Change the permission on the logging folder and ensure IIS_WPG group has write access to the folder. DO NOT restart IIS after changing the permission. - Launch our application and view another document. - At this point a logfile with a filename pattern described will be found in the logging folder. As mentioned, it is unlikely that permissions are the trigger in our event but it is likely that the same code is creating these unexpected patterns irrespective of the trigger.

How to find where log4net is logging to at runtime

lilalfyalien — 2008-09-18T10:47:54

Hi, I am using this code to load in an XML config file: FileInfo configFile = new FileInfo("C:\\Log4Net.Config"); log4net.Config.XmlConfigurator.ConfigureAndWatch(configFile); How can I then find out where Log4Net is logging to so I can display this info to my user and tell them to look in the log file at X? Thanks Amy

RollingFileAppender generates unexpected filename and/or causes IIS to hang

Iyer, Devan — 2008-09-16T20:09:36

We are using rolling file appender in an IIS managed C# application. Our log4Net deployment is configured with the following options specified in basic.xml: . The file pattern for our log file name is "abc_%date{yyyyMMdd_HHmmss}_%processid_.log". We have observed in our production environment that occasionally filenames would be created with patterns like "abc_%date{yyyyMMdd_HHmmss}_%processid_.log.1", "abc_%date{yyyyMMdd_HHmmss}_%processid_.log.1.2", "abc_%date{yyyyMMdd_HHmmss}_%processid_.log.1.2.3", etc. We have observed filenames with the dot+sequential numbers pattern after the .log to be anything from ".1" to ".220". This is one of two unexpected behaviours observed. The second unexpected behaviour seems to a special case of the first that occasionally causes IIS to hang (100% CPU consumption). An analysis of several crash dumps taken at the time of the hang indicated that RollingFileAppender had in memory a filename of the same pattern as above but with the number of characters [base filename pattern]+[recurring extension pattern] exceeding 255 characters. It is very likely that an attempt to create a file by such name on NTFS would throw exceptions at various levels - managed and native - and hence the file itself is never created. To the best of our knowledge, there were no events to trigger the filename to be rolled. As indicated in the configuration options, we are using RollingStyle of "Once". (The log file content is minimal at the time the symptoms occur - total file size is about 2K - and the times of occurrence are totally non related). We have been unable to capture the workflow leading up to the symptoms above due to the high number of users and document types in our production environment. The permissions on the logging folder are static. However, we have found a simple workflow in our lab environment, using permissions, that produce similar symptoms. This workflow is: - Right click on the logging folder and select "Properties" - Under the "Security" tab ensure that IIS_WPG group doesn't have write access to the logging folder. - Restart IIS - Launch our application and view a document. Check the logging folder to make sure that a logfile is not created. - View a few more documents - Change the permission on the logging folder and ensure IIS_WPG group has write access to the folder. DO NOT restart IIS after changing the permission. - Launch our application and view another document. - At this point a logfile with a filename pattern described will be found in the logging folder. As mentioned, it is unlikely that permissions are the trigger in our event but it is likely that the same code is creating these unexpected patterns irrespective of the trigger.

Same file read/write from Multiple process

Pradeeptp — 2008-09-11T12:27:02

Hi All, I am considering to use Log4Net in a web service to write to a single log file. I want to know whether writing to a single file in this manner through Log4Net is safe. The current code I have implemented is in C# in which I am writing to a single file which gives me error "The process cannot access the file XXXXX because it is beign used by another process" To resolve the above problem I am considering using Log4Net. If anyone has any experience in using Log4Net please confirm me that this error will not happen in Log4Net. Thanks pradeeptp

[jira] Created: (LOG4NET-174) log4net.dll references assemblies that are not part of the .NET 3.5 SP1 client profile

Kuno Meyer (JIRA — 2008-09-10T15:22:44

log4net.dll references assemblies that are not part of the .NET 3.5 SP1 client profile -------------------------------------------------------------------------------------- Key: LOG4NET-174 URL: https://issues.apache.org/jira/browse/LOG4NET-174 Project: Log4net Issue Type: Bug Components: Builds Affects Versions: 1.2.10 Environment: .Net 3.5 SP1 Reporter: Kuno Meyer .Net 3.5 SP1 / VS 2008 SP1 has a new build feature: the "client-only framework subset" switch in the projects settings, meaning that the developer can specify that only a limited subset of the .Net framework is used. This helps in reducing the size of installers that include the .Net framework. Unfortunately, log4net.dll (1.2.10) has references to System.Web, which is not part of this "client-only framework subset". This leads to the following compilation warning: <<< C:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets : warning MSB3253: The referenced assembly "log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=1b44e1d426115821, processorArchitecture=MSIL" has a dependency on "System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which is not listed as part of the "Client" TargetFrameworkSubset. If this dependent reference is required, you may get compilation errors. My proposal is to split log4net.dll into a new log4net.dll (core+generic appenders) and into a separate appender DLL (log4net.server.dll) for deployment on servers only.

[jira] Created: (LOG4NET-173) Request for NMS Appender

Mark Keenan (JIRA — 2008-09-02T19:23:44

Request for NMS Appender ------------------------ Key: LOG4NET-173 URL: https://issues.apache.org/jira/browse/LOG4NET-173 Project: Log4net Issue Type: Wish Components: Appenders Affects Versions: v.Next Reporter: Mark Keenan Priority: Minor Based on some messages in the ActiveMQ forum, I believe the NMS developers are getting close to a 1.0 release. An NMS based appender for log4net would be extremely useful. I'm not sure how much of the JMS appender could be ported from log4j but maybe that's a good starting point?

[jira] Created: (LOG4NET-172) Web Service Appender

Brandon Wood (JIRA — 2008-08-26T18:30:46

Web Service Appender -------------------- Key: LOG4NET-172 URL: https://issues.apache.org/jira/browse/LOG4NET-172 Project: Log4net Issue Type: New Feature Components: Appenders Reporter: Brandon Wood Priority: Minor Attachments: WebServiceAppender.cs I have created a web service appender for a project I'm working on, and would like to contribute the code to log4net.

svn commit: r688531 - in /logging/log4net/trunk/src: Core/TimeEvaluator.cs log4net.vs2005.csproj

2008-08-24T17:17:25

Author: rgrabowski Date: Sun Aug 24 10:17:25 2008 New Revision: 688531 URL: http://svn.apache.org/viewvc?rev=688531&view=rev Log: Fix for LOG4NET-155. Added TimeEvaluator that will trigger a buffer flush if a certain amount of time has elapsed since the last event. Added: logging/log4net/trunk/src/Core/TimeEvaluator.cs Modified: logging/log4net/trunk/src/log4net.vs2005.csproj Added: logging/log4net/trunk/src/Core/TimeEvaluator.cs URL: http://svn.apache.org/viewvc/logging/log4net/trunk/src/Core/TimeEvaluator.cs?rev=688531&view=auto ============================================================================== --- logging/log4net/trunk/src/Core/TimeEvaluator.cs (added) +++ logging/log4net/trunk/src/Core/TimeEvaluator.cs Sun Aug 24 10:17:25 2008 < at >< at > -0,0 +1,147 < at >< at > +#region Copyright & License +// +// Copyright 2001-2005 The Apache Software Foundation +// +// Licensed under the Apache License, Version 2.0 (the "License"); +// you may not use this file except in compliance with the License. +// You may obtain a copy of the License at +// +// http://www.apache.org/licenses/LICENSE-2.0 +// +// Unless required by applicable law or agreed to in writing, software +// distributed under the License is distributed on an "AS IS" BASIS, +// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +// See the License for the specific language governing permissions and +// limitations under the License. +// +#endregion + +using System; + +namespace log4net.Core +{ + ///

+ /// An evaluator that triggers after specified number of seconds. + ///

+ /// + /// + /// This evaluator will trigger if the specified time period + /// has passed since last check. + /// + /// + /// Robert Sevcik + public class TimeEvaluator : ITriggeringEventEvaluator + { + ///

+ /// The time threshold for triggering in seconds. Zero means it won't trigger at all. + ///

+ private int m_interval; + + ///

+ /// The time of last check. This gets updated when the object is created and when the evaluator triggers. + ///

+ private DateTime m_lasttime; + + ///

+ /// The default time threshold for triggering in seconds. Zero means it won't trigger at all. + ///

+ const int DEFAULT_INTERVAL = 0; + + ///

+ /// Create a new evaluator using the time threshold in seconds. + ///

+ /// + /// + /// Create a new evaluator using the time threshold in seconds. + /// + /// + /// This evaluator will trigger if the specified time period + /// has passed since last check. + /// + /// + public TimeEvaluator() + : this(DEFAULT_INTERVAL) + { + } + + ///

+ /// Create a new evaluator using the specified time threshold in seconds. + ///

+ /// + /// The time threshold in seconds to trigger after. + /// Zero means it won't trigger at all. + /// + /// + /// + /// Create a new evaluator using the specified time threshold in seconds. + /// + /// + /// This evaluator will trigger if the specified time period + /// has passed since last check. + /// + /// + public TimeEvaluator(int interval) + { + m_interval = interval; + m_lasttime = DateTime.Now; + } + + ///

+ /// The time threshold in seconds to trigger after + ///

+ /// + /// The time threshold in seconds to trigger after. + /// Zero means it won't trigger at all. + /// + /// + /// + /// This evaluator will trigger if the specified time period + /// has passed since last check. + /// + /// + public int Interval + { + get { return m_interval; } + set { m_interval = value; } + } + + ///

+ /// Is this the triggering event? + ///

+ /// The event to check + /// This method returns true, if the specified time period + /// has passed since last check.. + /// Otherwise it returns false + /// + /// + /// This evaluator will trigger if the specified time period + /// has passed since last check. + /// + /// + public bool IsTriggeringEvent(LoggingEvent loggingEvent) + { + if (loggingEvent == null) + { + throw new ArgumentNullException("loggingEvent"); + } + + // disable the evaluator if threshold is zero + if (m_interval == 0) return false; + + lock (this) // avoid triggering multiple times + { + TimeSpan passed = DateTime.Now.Subtract(m_lasttime); + + if (passed.TotalSeconds > m_interval) + { + m_lasttime = DateTime.Now; + return true; + } + else + { + return false; + } + } + } + } +} Modified: logging/log4net/trunk/src/log4net.vs2005.csproj URL: http://svn.apache.org/viewvc/logging/log4net/trunk/src/log4net.vs2005.csproj?rev=688531&r1=688530&r2=688531&view=diff ============================================================================== --- logging/log4net/trunk/src/log4net.vs2005.csproj (original) +++ logging/log4net/trunk/src/log4net.vs2005.csproj Sun Aug 24 10:17:25 2008 < at >< at > -281,6 +281,7 < at >< at > Code + Code

svn commit: r688527 - /logging/log4net/trunk/src/Config/XmlConfigurator.cs

2008-08-24T17:00:03

Author: rgrabowski Date: Sun Aug 24 10:00:02 2008 New Revision: 688527 URL: http://svn.apache.org/viewvc?rev=688527&view=rev Log: Fix for LOG4NET-158. XMLConfigurator.ConfigureAndWatch() won't leak resources when called multiple times. Internal FileWatcher is properly disposed when a change is detected. Modified: logging/log4net/trunk/src/Config/XmlConfigurator.cs Modified: logging/log4net/trunk/src/Config/XmlConfigurator.cs URL: http://svn.apache.org/viewvc/logging/log4net/trunk/src/Config/XmlConfigurator.cs?rev=688527&r1=688526&r2=688527&view=diff ============================================================================== --- logging/log4net/trunk/src/Config/XmlConfigurator.cs (original) +++ logging/log4net/trunk/src/Config/XmlConfigurator.cs Sun Aug 24 10:00:02 2008 < at >< at > -870,9 +870,23 < at >< at > try { -// Create a watch handler that will reload the -// configuration whenever the config file is modified. -ConfigureAndWatchHandler.StartWatching(repository, configFile); + lock (m_repositoryName2ConfigAndWatchHandler) + { + // support multiple repositories each having their own watcher + ConfigureAndWatchHandler handler = + (ConfigureAndWatchHandler)m_repositoryName2ConfigAndWatchHandler[repository.Name]; + + if (handler != null) + { + m_repositoryName2ConfigAndWatchHandler.Remove(repository.Name); + handler.Dispose(); + } + + // Create and start a watch handler that will reload the + // configuration whenever the config file is modified. + handler = new ConfigureAndWatchHandler(repository, configFile); + m_repositoryName2ConfigAndWatchHandler[repository.Name] = handler; + } } catch(Exception ex) { < at >< at > -903,24 +917,9 < at >< at > /// elapse. /// /// -private sealed class ConfigureAndWatchHandler +private sealed class ConfigureAndWatchHandler : IDisposable { ///

-/// Watch a specified config file used to configure a repository -///

-/// The repository to configure. -/// The configuration file to watch. -/// -/// -/// Watch a specified config file used to configure a repository -/// -/// -internal static void StartWatching(ILoggerRepository repository, FileInfo configFile) -{ -new ConfigureAndWatchHandler(repository, configFile); -} - -///

/// Holds the FileInfo used to configure the XmlConfigurator ///

private FileInfo m_configFile; < at >< at > -941,8 +940,15 < at >< at > /// private const int TimeoutMillis = 500; + ///

+ /// Watches file for changes. This object should be disposed when no longer + /// needed to free system handles on the watched resources. + ///

+ private FileSystemWatcher m_watcher; + ///

-/// Initializes a new instance of the class. +/// Initializes a new instance of the class to + /// watch a specified config file used to configure a repository. ///

/// The repository to configure. /// The configuration file to watch. < at >< at > -951,31 +957,31 < at >< at > /// Initializes a new instance of the class. /// /// -private ConfigureAndWatchHandler(ILoggerRepository repository, FileInfo configFile) +public ConfigureAndWatchHandler(ILoggerRepository repository, FileInfo configFile) { m_repository = repository; m_configFile = configFile; // Create a new FileSystemWatcher and set its properties. -FileSystemWatcher watcher = new FileSystemWatcher(); +m_watcher = new FileSystemWatcher(); -watcher.Path = m_configFile.DirectoryName; -watcher.Filter = m_configFile.Name; +m_watcher.Path = m_configFile.DirectoryName; +m_watcher.Filter = m_configFile.Name; // Set the notification filters -watcher.NotifyFilter = NotifyFilters.CreationTime | NotifyFilters.LastWrite | NotifyFilters.FileName; +m_watcher.NotifyFilter = NotifyFilters.CreationTime | NotifyFilters.LastWrite | NotifyFilters.FileName; // Add event handlers. OnChanged will do for all event handlers that fire a FileSystemEventArgs -watcher.Changed += new FileSystemEventHandler(ConfigureAndWatchHandler_OnChanged); -watcher.Created += new FileSystemEventHandler(ConfigureAndWatchHandler_OnChanged); -watcher.Deleted += new FileSystemEventHandler(ConfigureAndWatchHandler_OnChanged); -watcher.Renamed += new RenamedEventHandler(ConfigureAndWatchHandler_OnRenamed); +m_watcher.Changed += new FileSystemEventHandler(ConfigureAndWatchHandler_OnChanged); +m_watcher.Created += new FileSystemEventHandler(ConfigureAndWatchHandler_OnChanged); +m_watcher.Deleted += new FileSystemEventHandler(ConfigureAndWatchHandler_OnChanged); +m_watcher.Renamed += new RenamedEventHandler(ConfigureAndWatchHandler_OnRenamed); // Begin watching. -watcher.EnableRaisingEvents = true; +m_watcher.EnableRaisingEvents = true; // Create the timer that will be used to deliver events. Set as disabled -m_timer = new Timer(new TimerCallback(OnWatchedFileChange), null, Timeout.Infinite, Timeout.Infinite); + m_timer = new Timer(new TimerCallback(OnWatchedFileChange), null, Timeout.Infinite, Timeout.Infinite); } ///

< at >< at > -1024,6 +1030,16 < at >< at > { XmlConfigurator.InternalConfigure(m_repository, m_configFile); } + + ///

+ /// Release the handles held by the watcher and timer. + ///

+ public void Dispose() + { + m_watcher.EnableRaisingEvents = false; + m_watcher.Dispose(); + m_timer.Dispose(); + } } #endif < at >< at > -1083,6 +1099,13 < at >< at > #region Private Static Fields + ///

+ /// Maps repository names to ConfigAndWatchHandler instances to allow a particular + /// ConfigAndWatchHandler to dispose of its FileSystemWatcher when a repository is + /// reconfigured. + ///

+ private readonly static Hashtable m_repositoryName2ConfigAndWatchHandler = new Hashtable(); + ///

/// The fully qualified type of the XmlConfigurator class. ///

svn commit: r688521 - /logging/log4net/trunk/xdocs/src/release/example-apps.xml

2008-08-24T15:42:33

Author: rgrabowski Date: Sun Aug 24 08:42:32 2008 New Revision: 688521 URL: http://svn.apache.org/viewvc?rev=688521&view=rev Log: Fix for LOG4NET-126. Changed link to downloads page from "downloads.html" to "download.html". Modified: logging/log4net/trunk/xdocs/src/release/example-apps.xml Modified: logging/log4net/trunk/xdocs/src/release/example-apps.xml URL: http://svn.apache.org/viewvc/logging/log4net/trunk/xdocs/src/release/example-apps.xml?rev=688521&r1=688520&r2=688521&view=diff ============================================================================== --- logging/log4net/trunk/xdocs/src/release/example-apps.xml (original) +++ logging/log4net/trunk/xdocs/src/release/example-apps.xml Sun Aug 24 08:42:32 2008 < at >< at > -63,7 +63,7 < at >< at >

The following examples are only available in the log4net release download, not - on-line. To obtain the examples download one of the log4net releases. + on-line. To obtain the examples download one of the log4net releases.

svn commit: r688416 - /logging/log4net/trunk/src/Appender/SmtpAppender.cs

2008-08-23T21:14:25

Author: rgrabowski Date: Sat Aug 23 14:14:24 2008 New Revision: 688416 URL: http://svn.apache.org/viewvc?rev=688416&view=rev Log: Fix for LOG4NET-128. Explain the comma/semicolon differences between various versions of the Framework. Modified: logging/log4net/trunk/src/Appender/SmtpAppender.cs Modified: logging/log4net/trunk/src/Appender/SmtpAppender.cs URL: http://svn.apache.org/viewvc/logging/log4net/trunk/src/Appender/SmtpAppender.cs?rev=688416&r1=688415&r2=688416&view=diff ============================================================================== --- logging/log4net/trunk/src/Appender/SmtpAppender.cs (original) +++ logging/log4net/trunk/src/Appender/SmtpAppender.cs Sat Aug 23 14:14:24 2008 < at >< at > -92,12 +92,20 < at >< at > /// Gets or sets a semicolon-delimited list of recipient e-mail addresses. /// /// -/// A semicolon-delimited list of e-mail addresses. + /// + /// For .NET 1.1 (System.Web.Mail): A semicolon-delimited list of e-mail addresses. + /// + /// + /// For .NET 2.0 (System.Net.Mail): A comma-delimited list of e-mail addresses. + /// /// /// -/// -/// A semicolon-delimited list of recipient e-mail addresses. -/// + /// + /// For .NET 1.1 (System.Web.Mail): A semicolon-delimited list of e-mail addresses. + /// + /// + /// For .NET 2.0 (System.Net.Mail): A comma-delimited list of e-mail addresses. + /// /// public string To { < at >< at > -110,11 +118,19 < at >< at > /// that will be carbon copied. /// /// - /// A semicolon-delimited list of e-mail addresses. + /// + /// For .NET 1.1 (System.Web.Mail): A semicolon-delimited list of e-mail addresses. + /// + /// + /// For .NET 2.0 (System.Net.Mail): A comma-delimited list of e-mail addresses. + /// /// /// /// - /// A semicolon-delimited list of recipient e-mail addresses. + /// For .NET 1.1 (System.Web.Mail): A semicolon-delimited list of e-mail addresses. + /// + /// + /// For .NET 2.0 (System.Net.Mail): A comma-delimited list of e-mail addresses. /// /// public string Cc

svn commit: r688413 - /logging/log4net/trunk/src/Appender/SmtpAppender.cs

2008-08-23T21:06:29

Author: rgrabowski Date: Sat Aug 23 14:06:28 2008 New Revision: 688413 URL: http://svn.apache.org/viewvc?rev=688413&view=rev Log: Fix for LOG4NET-168. Add ReplyTo property to SmtpAppender. Modified: logging/log4net/trunk/src/Appender/SmtpAppender.cs Modified: logging/log4net/trunk/src/Appender/SmtpAppender.cs URL: http://svn.apache.org/viewvc/logging/log4net/trunk/src/Appender/SmtpAppender.cs?rev=688413&r1=688412&r2=688413&view=diff ============================================================================== --- logging/log4net/trunk/src/Appender/SmtpAppender.cs (original) +++ logging/log4net/trunk/src/Appender/SmtpAppender.cs Sat Aug 23 14:06:28 2008 < at >< at > -319,6 +319,18 < at >< at > get { return m_enableSsl; } set { m_enableSsl = value; } } + + ///

+ /// Gets or sets the reply-to e-mail address. + ///

+ /// + /// This is available on MS .NET 2.0 runtime and higher + /// + public string ReplyTo + { + get { return m_replyTo; } + set { m_replyTo = value; } + } #endif #endregion // Public Instance Properties < at >< at > -398,7 +410,7 < at >< at > // Create and configure the smtp client SmtpClient smtpClient = new SmtpClient(); -if (m_smtpHost != null && m_smtpHost.Length > 0) +if (!String.IsNullOrEmpty(m_smtpHost)) { smtpClient.Host = m_smtpHost; } < at >< at > -429,6 +441,10 < at >< at > { mailMessage.Bcc.Add(m_bcc); } + if (!String.IsNullOrEmpty(m_replyTo)) + { + mailMessage.ReplyTo = new MailAddress(m_replyTo); + } mailMessage.Subject = m_subject; mailMessage.Priority = m_mailPriority; < at >< at > -533,6 +549,7 < at >< at > #if NET_2_0 private bool m_enableSsl = false; + private string m_replyTo; #endif #endregion // Private Instance Fields

svn commit: r688397 - in /logging/log4net/trunk: src/Core/LoggingEvent.cs xdocs/src/release/manual/contexts.xml

2008-08-23T18:56:17

Author: rgrabowski Date: Sat Aug 23 11:56:17 2008 New Revision: 688397 URL: http://svn.apache.org/viewvc?rev=688397&view=rev Log: Fix for LOG4NET-140. Improve documentation for IFixingRequired to explain how data can be evaluated immediately when a logging event is created or delayed until being written to an appender. Modified: logging/log4net/trunk/src/Core/LoggingEvent.cs logging/log4net/trunk/xdocs/src/release/manual/contexts.xml Modified: logging/log4net/trunk/src/Core/LoggingEvent.cs URL: http://svn.apache.org/viewvc/logging/log4net/trunk/src/Core/LoggingEvent.cs?rev=688397&r1=688396&r2=688397&view=diff ============================================================================== --- logging/log4net/trunk/src/Core/LoggingEvent.cs (original) +++ logging/log4net/trunk/src/Core/LoggingEvent.cs Sat Aug 23 11:56:17 2008 < at >< at > -228,7 +228,7 < at >< at > Exception = 0x100, ///

-/// Fix the event properties +/// Fix the event properties. Active properties must implement in order to be eligible for fixing. ///

Properties = 0x200, Modified: logging/log4net/trunk/xdocs/src/release/manual/contexts.xml URL: http://svn.apache.org/viewvc/logging/log4net/trunk/xdocs/src/release/manual/contexts.xml?rev=688397&r1=688396&r2=688397&view=diff ============================================================================== --- logging/log4net/trunk/xdocs/src/release/manual/contexts.xml (original) +++ logging/log4net/trunk/xdocs/src/release/manual/contexts.xml Sat Aug 23 11:56:17 2008 < at >< at > -149,9 +149,28 < at >< at > string by calling the ToString method the current number of bytes allocated by the garbage collector will be returned and included in the output.

- - - +

+Note that the ToStringmethod will not be +called until the LoggingEventis rendered, as +explained in the Fixingsection. An active property +is not eligible to be fixed unless it implements + IFixingRequired. +

+ + + +

+Some properties, e.g. the current thread property, or any +active properties, are not realised +until their containing LoggingEventis rendered. If the +LoggingEventis been sent to a buffering appender (such as +AdoNetAppender) then this rendering will not happen +unless the +BufferingAppenderSkeleton's +Fix propertyhas been set. In addition, an active property is not eligible to be fixed unless it implements +IFixingRequired. +

[jira] Created: (LOG4NET-171) Log file locking causing an error to be thrown from the RollingFileAppender

Steven Myron (JIRA — 2008-08-22T21:00:45

Log file locking causing an error to be thrown from the RollingFileAppender --------------------------------------------------------------------------- Key: LOG4NET-171 URL: https://issues.apache.org/jira/browse/LOG4NET-171 Project: Log4net Issue Type: Bug Components: Core Affects Versions: 1.2.10 Environment: Windows 2003 Server (scheduled jobs/.exe that may be overlapping) Reporter: Steven Myron Priority: Critical Scheduled processes (~ 15 minutes apart) seem to be overlapping possibly causing file sharing violations for the log file that log4net is writing to. This file is statically named and is written to using the RollingFileAppender. This abruptly terminates the application and presents an unexpected error to the client.

[jira] Created: (LOG4NET-170) Documentation improvement re: fixing and active properties

Jerry Shea (JIRA — 2008-08-22T11:42:44

Documentation improvement re: fixing and active properties ---------------------------------------------------------- Key: LOG4NET-170 URL: https://issues.apache.org/jira/browse/LOG4NET-170 Project: Log4net Issue Type: Improvement Components: Documentation Affects Versions: 1.2.10 Reporter: Jerry Shea Priority: Minor Documentation improvement - see http://www.nabble.com/ASP.NET%2C-AdoNetAppender-and-deferred-property-execution-tt18865968.html