Michael Grondines created LOG4NET-440: -----------------------------------------
Summary: 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 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)