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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.9.1.0
• Fix Version/s: 10.8.3.0, 10.9.2.2, 10.10.1.1
• Component/s: Services
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 23/Jun/12 11:42
• Updated: 02/May/13 02:29
• Resolved: 09/Jul/12 11:16

Description

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.

Issue Links

• is depended upon by: DERBY-4269 Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK