[logback-dev] [JIRA] Resolved: (LBCORE-104) Entry key/value if removed from the Property file, still exist as properties of the execution context

[Ceki Gulcu (JIRA)]

     [ http://jira.qos.ch/browse/LBCORE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ceki Gulcu resolved LBCORE-104.
-------------------------------

    Fix Version/s: 0.9.16
       Resolution: Fixed

Fixed in revision 2316, to be released in 0.9.16.

> Entry key/value if removed from the Property file, still exist as properties of the execution context
> -----------------------------------------------------------------------------------------------------
>
>                 Key: LBCORE-104
>                 URL: http://jira.qos.ch/browse/LBCORE-104
>             Project: logback-core
>          Issue Type: Bug
>          Components: Joran
>    Affects Versions: 0.9.15
>         Environment: Windows XP, Tomcat 5.0.27, Java 1.5 Sun JVM
>            Reporter: Johan Bos
>            Assignee: Logback dev list
>             Fix For: 0.9.16
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira