You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2012/06/25 15:37:43 UTC
[jira] [Commented] (DERBY-5830) Make
DoubleProperties.propertyNames() thread-safe
[ 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