[jira] [Updated] (DERBY-5830) Make DoubleProperties.propertyNames() thread-safe

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-5830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen updated DERBY-5830:
--------------------------------------

    Attachment: keys-only-v2.diff

Attaching keys-only-v2.diff, based on keys-only.diff attached to DERBY-4269. The patch removes the unnecessary calls to Properties.getProperty(). Unlike the original keys-only.diff, it uses a HashSet to store the set of property names so that duplicate names are removed automatically.

Both suites.All and derbyall ran cleanly with the patch.
                
> 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