[jira] [Commented] (CONFIGURATION-530) AbstractFileConfiguration.getProperty(String key) locking causes thread halt

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (CONFIGURATION-530) AbstractFileConfiguration.getProperty(String key) locking causes thread halt

Lars Bruun-Hansen (Jira)

    [ https://issues.apache.org/jira/browse/CONFIGURATION-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604703#comment-13604703 ]

Oliver Heger commented on CONFIGURATION-530:
--------------------------------------------

Version 2 will not be backwards compatible, there are some major design changes.

AFAICT, there is currently no interest in working on the 1.x branch. Also, I am not sure whether the problems related to relading can be changed with reasonable effort and without breaking existing applications.
               

> AbstractFileConfiguration.getProperty(String key) locking causes thread halt
> ----------------------------------------------------------------------------
>
>                 Key: CONFIGURATION-530
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-530
>             Project: Commons Configuration
>          Issue Type: Bug
>          Components: File reloading
>    Affects Versions: 1.9
>            Reporter: yair ogen
>            Priority: Critical
>
> Every call to getProperty causes a lock (related to the reload functionality). In a near real-time system where we have many concurrent threads this affects heavily on the application TPS.
> Possible solution will be: getProperty only returns current value. Reload when needed occurs in a background thread that updates the in-memory map (perhaps by using CopyOnWrite collections?).

--
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