[
https://issues.apache.org/jira/browse/CONFIGURATION-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved CONFIGURATION-330.
----------------------------------------
Resolution: Fixed
In version 2.0 reloading and synchronized access to configurations have been
completely redesigned. A so-called {{Synchronizer}} is now used to control
concurrent access to a configuration. While the default synchronizer is just a
dummy, applications can change it according to their use cases. There is also
an implementation of {{Synchronizer}} based on the JDK's
{{ReentrantReadWriteLock}} class.
> Thread safety for file based configurations
> -------------------------------------------
>
> Key: CONFIGURATION-330
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-330
> Project: Commons Configuration
> Issue Type: Improvement
> Affects Versions: 1.5
> Reporter: Emmanuel Bourg
> Fix For: 2.0
>
>
> When autoSave is enabled on a FileConfiguration it's quite frequent to run
> into a ConcurrentModificationException, simply because setProperty is called
> from a thread while another thread is saving the configuration.
> I suggest to leverage the ReadWriteLock in Java 5 to solve this issue. The
> read lock is acquired in getProperty(), and the write lock is acquired in
> setProperty().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
