Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4NET Dev" <log4net-dev@logging.apache.org>
Date: Tue, 28 Jan 2014 12:52:38 +0000 (UTC)
From: "Mat Arge (JIRA)" <jira@apache.org>
To: log4net-dev@logging.apache.org
Message-ID: <JIRA.12691617.1390909038938.25824.1390913558227@arcas>
In-Reply-To: <JIRA.12691617.1390909038938@arcas>
References: <JIRA.12691617.1390909038938@arcas>
Subject: [jira] [Commented] (LOG4NET-420) Destructor of class called upon
 invoking XmlConfigurator.Configure
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LOG4NET-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884083#comment-13884083 ] 

Mat Arge commented on LOG4NET-420:
----------------------------------

But the object is destroyed right after (during) the call to Configure. At this point, there is still an active reference to the object so the Garbage Collector should not claim it.

> 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)