[
https://issues.apache.org/jira/browse/LOG4NET-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-420.
-----------------------------------
Resolution: Not A Problem
Destroying objects is the job of the finalizer. log4net has nothing to deal
with that. The thing that matters is garbage collection, just in case you want
to understand how that works.
> Destructor of class called upon invoking XmlConfigurator.Configure
> ------------------------------------------------------------------
>
> Key: LOG4NET-420
> URL: https://issues.apache.org/jira/browse/LOG4NET-420
> Project: Log4net
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.10, 1.2.13
> Environment: Linux (openSuse 12.2 i586), Mono 2.10.9
> Reporter: Mat Arge
>
> If I run XmlConfigurator.Configure on an XML File after an instance of some
> class has been created, the destructor of that class is called for some
> reason. Here is my test code:
> using System;
>
> public class Test
> {
> ~Test()
> {
> Console.WriteLine("Test object finalized.");
> }
> }
> public static class M
> {
> public static void Main()
> {
> Console.WriteLine("Start");
> Test test = new Test();
> Console.WriteLine("configuring");
> log4net.Config.XmlConfigurator.Configure(new
> System.IO.FileInfo("LogConfiguration.xml"));
> Console.WriteLine("End");
> }
> }
> Running this yields the output:
> Start
> configuring
> Test object finalized.
> End
> I'm not really sure, if this is a bug in log4net or in mono
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
