Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 25 Jun 2012 13:37:43 +0000 (UTC)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <446418659.50937.1340631463456.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1496546617.47488.1340451762786.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (DERBY-5830) Make
 DoubleProperties.propertyNames() thread-safe
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dag H. Wanvik commented on DERBY-5830:
--------------------------------------

Looks like a good improvement in its own right. +1

                
> Make DoubleProperties.propertyNames() thread-safe
> -------------------------------------------------
>
>                 Key: DERBY-5830
>                 URL: https://issues.apache.org/jira/browse/DERBY-5830
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions: 10.9.1.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: keys-only-v2.diff
>
>
> As discussed in DERBY-4269, DoubleProperties.propertyNames() may throw a NullPointerException if properties are removed by another thread while the method is executing. Since DoubleProperties is a sub-class of, and used as a drop-in replacement for, java.util.Properties, it should be thread-safe just like the propertyNames() method in the parent class.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira