Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <1920137095.98051265475927998.JavaMail.jira@brutus.apache.org>
Date: Sat, 6 Feb 2010 17:05:27 +0000 (UTC)
From: "Oliver Heger (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Created: (CONFIGURATION-407)
 HierarchicalINIConfiguration.getSection() is not thread-safe if the global
 section is requested
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

HierarchicalINIConfiguration.getSection() is not thread-safe if the global section is requested
-----------------------------------------------------------------------------------------------

                 Key: CONFIGURATION-407
                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-407
             Project: Commons Configuration
          Issue Type: Bug
    Affects Versions: 1.6
            Reporter: Oliver Heger


If the global section of a hierarchical INI configuration is requested, a new ViewNode is created which becomes the root node of a new configuration for the global section. Nodes representing properties of the global section are added to this ViewNode. This operation temporarily changes the parent node of these nodes which may cause problems if the method is called by multiple threads concurrently. Because access to a section is a read-only operation, this should be thread-safe.

The probability that this error happens is pretty low IMO. Therefore it should be hard to create a unit test.

The issue can be fixed by synchronizing the add operation to the ViewNode.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.