[
https://issues.apache.org/jira/browse/CONFIGURATION-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated CONFIGURATION-330:
-----------------------------------------
Affects Version/s: 1.5
Fix Version/s: 2.0
> 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.
-
You can reply to this email to add a comment to the issue online.