Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Tue, 4 Jun 2013 19:45:21 +0000 (UTC)
From: "Oliver Heger (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12636235.1362920083771.66506.1370375121201@arcas>
In-Reply-To: <JIRA.12636235.1362920083771@arcas>
References: <JIRA.12636235.1362920083771@arcas>
Subject: [jira] [Commented] (CONFIGURATION-530)
 AbstractFileConfiguration.getProperty(String key) locking causes thread
 halt
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Unfortunately, there is not yet a concrete release schedule. There are still some important points open which need to be fixed before a release.

Because of all these incompatible changes (parts of the API have been completely redesigned) it certainly makes sense to get out some alpha or beta releases first to get feedback from the community.
                
> 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
>             Fix For: 2.0
>
>
> 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