You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "yair ogen (JIRA)" <ji...@apache.org> on 2013/03/17 14:13:14 UTC

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

     [ https://issues.apache.org/jira/browse/CONFIGURATION-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

yair ogen updated CONFIGURATION-530:
------------------------------------

    Summary: AbstractFileConfiguration.getProperty(String key) locking causes thread halt  (was: AbstractFileConfiguration.getProperty(String key) locking causes thread hault)
    
> 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