[
https://issues.apache.org/jira/browse/CONFIGURATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved CONFIGURATION-136.
----------------------------------------
Resolution: Fixed
Fix Version/s: 2.0
This has been solved by the rework of the reloading mechanism which is now
handled by configuration builders.
> Reloading may corrupt the configuration
> ---------------------------------------
>
> Key: CONFIGURATION-136
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-136
> Project: Commons Configuration
> Issue Type: Bug
> Components: File reloading
> Affects Versions: 1.1
> Reporter: nicolas de loof
> Fix For: 2.0
>
> Attachments: commons-configuration-1.5_patch_CONFIGURATION-136.jar,
> commons-configuration-1.8_patch_CONFIGURATION-136.jar, patch.txt
>
>
> Current reloading process clears current properties and load updated values
> from
> resource reader. If an IO error occurs (or invalid format), the configuration
> gets corrupted and the application becomes unstable.
> It may be better for hot-reload to put loaded values into a temporary
> Properties
> and replace previous values only when reloading is successful.
> It may also allow to use a 'currentlty-reloading' flag in the synchronized
> 'reload' block to avoid blocking threads during a reload (they could access
> safelly the 'old' properties until reload is finished)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
