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

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.2.1.6, 10.3.1.4
• Component/s: Services
• Labels: derby_triage10_5_2
• Urgency: Normal
• Issue & fix info: Repro attached
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Created: 27/Oct/06 16:28
• Updated: 15/Feb/11 21:09

Description

Simple script that shows the problem, requires a database db with a table T.
First timeout wait is 60 seconds (default), next is 4 seconds (the setting), next is 4 seconds when it should be 60 the default.

connect 'jdbc:derby:db' AS C1;
AUTOCOMMIT OFF;
LOCK TABLE T IN EXCLUSIVE MODE;
connect 'jdbc:derby:db' AS C2;
– Default wait;
VALUES CURRENT TIMESTAMP;
LOCK TABLE T IN EXCLUSIVE MODE;
VALUES CURRENT TIMESTAMP;

– 4 second wait
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
'derby.locks.waitTimeout', '4');
VALUES CURRENT TIMESTAMP;
LOCK TABLE T IN EXCLUSIVE MODE;
VALUES CURRENT TIMESTAMP;

– back to default
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
'derby.locks.waitTimeout', null);
VALUES CURRENT TIMESTAMP;
LOCK TABLE T IN EXCLUSIVE MODE;
VALUES CURRENT TIMESTAMP;

Issue Links

• is related to: DERBY-1762 Setting the derby.locks.waitTimeout as a system property using System.setProperty does not affect booted databases