db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5830) Make DoubleProperties.propertyNames() thread-safe
Date Tue, 26 Jun 2012 08:14:43 GMT

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

Knut Anders Hatlen commented on DERBY-5830:

Thanks, Dag. Committed revision 1353852.

I'm also planning to backport this fix to 10.9, and possibly 10.8.
> 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:
>            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


View raw message