Uploaded image for project: 'Log4net'
  1. Log4net
  2. LOG4NET-440

Hierarchy does not reset loggers on configuration changes

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Not A Problem
    • Affects Version/s: 1.2.13
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None
    • Environment:
      .Net framework application(s)

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mgrondines Michael Grondines
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 48h
                48h
                Remaining:
                Remaining Estimate - 48h
                48h
                Logged:
                Time Spent - Not Specified
                Not Specified