[DERBY-1762] Setting the derby.locks.waitTimeout as a system property using System.setProperty does not affect booted databases

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Invalid
• Affects Version/s: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.3.1.4
• Component/s: Documentation, Services
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Created: 25/Aug/06 04:22
• Updated: 21/Jan/11 17:49
• Resolved: 09/Jul/09 10:19

Description

Tuning guide for derby.locks.waitTimeout states it is a dynamic property, but when set as a system property using System.setProperty it does not change the timeout for any databases already booted. It might change it for databases that are booted after the change, I didn't test that.

If the property is set as a database property then it is dynamic, taking effect immediately.

Guess it affects all versions.

Issue Links

• relates to: DERBY-2010 Unsetting derby.locks.waitTimeout as a database property does not reset the wait timeout to the default value.