intermittent test failure in store/lockTableVTI.sql
---------------------------------------------------
Key: DERBY-5630
URL: https://issues.apache.org/jira/browse/DERBY-5630
Project: Derby
Issue Type: Bug
Components: Test
Affects Versions: 10.8.2.3
Environment: Windows 2008, ibm 1.6 SR9 FP1, ibm 1.4.2.
Reporter: Myrna van Lunteren
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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
