[DERBY-5630] intermittent test failure in store/lockTableVTI.sql

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.8.3.0, 10.10.2.0
• Fix Version/s: 10.8.3.3, 10.9.2.2, 10.10.2.0, 11.0.0.0
• Component/s: Test
• Labels: derby_triage10_10
• Environment: Windows 2008, ibm 1.6 SR9 FP1, ibm 1.4.2.
• Urgency: Normal
• Issue & fix info: Patch Available
• Bug behavior facts: Regression Test Failure
• Assignee: Myrna van Lunteren
• Reporter: Myrna van Lunteren
• Created: 24/Feb/12 18:58
• Updated: 16/Apr/14 02:41
• Resolved: 10/Feb/14 18:57

Description

I've seen this test fail twice recently, once with ibm 1.6, once with 1.4.2, both times on the same machine (which is running 10.8 nightly testing):

The diff is as follows:
51a52,61
> ij(C1)> commit;
> ij(C1)> call SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.locks.waitTimeout', '180');
> 0 rows inserted/updated/deleted
> ij(C1)> commit;
> ij(C1)> set connection c2 ;
> ij(C2)> wait for C2S1;
> 3 rows inserted/updated/deleted
> ij(C2)> select state from syscs_diag.lock_table order by state;
> STATE
> -----
53,63d62
< WAIT
< ij(C1)> commit;
< ij(C1)> call SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.locks.waitTimeout', '180');
< 0 rows inserted/updated/deleted
< ij(C1)> commit;
< ij(C1)> set connection c2 ;
< ij(C2)> wait for C2S1;
< 3 rows inserted/updated/deleted
< ij(C2)> select state from syscs_diag.lock_table order by state;
< STATE
< -----
67d65
< GRANT

Issue Links

• is related to: DERBY-6275 address selective intermittent test failures before 10.10.2 release for 2-week clean goal.