Setting the derby.locks.waitTimeout as a system property using
System.setProperty does not affect booted databases
------------------------------------------------------------------------------------------------------------------
Key: DERBY-1762
URL: http://issues.apache.org/jira/browse/DERBY-1762
Project: Derby
Issue Type: Bug
Components: Documentation, Services
Affects Versions: 10.1.3.1, 10.1.3.0, 10.1.2.1, 10.1.1.0, 10.0.2.1,
10.0.2.0, 10.2.1.0, 10.3.0.0
Reporter: Daniel John Debrunner
Priority: Minor
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
