[
https://issues.apache.org/jira/browse/LOG4NET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Grondines closed LOG4NET-440.
-------------------------------------
Resolution: Not a Problem
Need to put the update mode to "Overwrite" instead of the default "Merge"
<log4net update="Overwrite">
> Hierarchy does not reset loggers on configuration changes
> ---------------------------------------------------------
>
> Key: LOG4NET-440
> URL: https://issues.apache.org/jira/browse/LOG4NET-440
> Project: Log4net
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.13
> Environment: .Net framework application(s)
> Reporter: Michael Grondines
> Priority: Minor
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Hi,
> We are using log4net in an application in .Net 3.5 where we cant to log
> things via hierarchically using the assemblies. For instance we have :
> "Program.Sub.Utilities"
> Each classes contained within the application have a static member with the
> logger instance using :
> LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType)
> For the configuration we are using the XmlConfigurator. Now, if we add a
> Logger for "Program.Sub" with level DEBUG, save, and then change the name of
> the logger for "Program.Sub.Utilities", we are still getting logs from stuff
> in "Program.Sub" !
> Looks like the first instance of the logger stays enabled, even if it's gone
> in the config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
