Uploaded image for project: 'logback'
  1. logback
  2. LOGBACK-103

Entry key/value if removed from the Property file, still exist as properties of the execution context

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: logback-core
    • Labels:
      None
    • Environment:

      Windows XP, Tomcat 5.0.27, Java 1.5 Sun JVM

      Description

      When logback.xml has a property file declaration.

      keys/values from the property file are not cleaned out from the configuration... they are overwritten in case they already exist.

      Which means that if the properties change while the application is loaded, and dynamically I reload the Logback configuration... the property file linked to it will only take into account new key or new values... removed key/value are still available in the context.

      InterpretationContext allows the LoggerContext to use the properties but the reset() method on the LoggerContext doesn't flush properties loaded.

      Is there a workaround? If so, pass the bug to Minor! I just found this annoying in case of a dynamical reload of configuration where even after reset, some setting are still present.

      Thanks.

        Attachments

          Activity

            People

            • Assignee:
              logback-dev Logback dev list
              Reporter:
              jbos Johan Bos
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: