Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 18445 invoked from network); 22 Feb 2006 15:13:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Feb 2006 15:13:13 -0000 Received: (qmail 67581 invoked by uid 500); 22 Feb 2006 15:13:06 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 67539 invoked by uid 500); 22 Feb 2006 15:13:06 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 67528 invoked by uid 99); 22 Feb 2006 15:13:06 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Feb 2006 07:13:06 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [137.248.254.139] (HELO pm.med.uni-marburg.de) (137.248.254.139) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Feb 2006 07:13:04 -0800 Received: from pm.med.uni-marburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A0B2263D7E for ; Wed, 22 Feb 2006 16:12:42 +0100 (CET) Received: from post.med.uni-marburg.de (unknown [172.31.100.100]) by pm.med.uni-marburg.de (Postfix) with ESMTP id 9BFF363D7A for ; Wed, 22 Feb 2006 16:12:42 +0100 (CET) Received: from [137.248.224.93] (wstlehre93.med.uni-marburg.de [137.248.224.93]) by post.med.uni-marburg.de (Postfix) with ESMTP id 8E3E07FEA for ; Wed, 22 Feb 2006 16:12:42 +0100 (CET) Message-ID: <43FC7F6A.6050206@med.uni-marburg.de> Date: Wed, 22 Feb 2006 16:12:42 +0100 From: Oliver Heger User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: de, de-at, en-us, en MIME-Version: 1.0 To: Jakarta Commons Users List Subject: Re: [Configuration] thread-safe? References: <022401c637be$4682d0d0$693e6780@ca.harvard.edu> In-Reply-To: <022401c637be$4682d0d0$693e6780@ca.harvard.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Mike Ferraro wrote: > I apologize if this question has been answered, but couldn't seem to > find a search function for the mailing list archives. > > Can anyone tell me if the Commons Configuration tools are thread safe? > Specifically, I would like to maintain a global CompositeConfiguration > within a web application that contains several FileConfigurations with > active reload strategies. I want to make sure that there aren't any > collisions when seperate threads are attempting to access properties on > the same configuration, especially during a reload. > > Any idea if this is built in, or do I have to worry about doing this > myself? > Read only access to a Configuration object should be thread-safe. This also includes reloading activities (during a reload operation an explicit lock is hold). However if some of your threads update the configuration, you are responsible for synchronization yourself. HTH Oliver --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org