db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5630) intermittent test failure in store/lockTableVTI.sql
Date Tue, 04 Feb 2014 05:02:08 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren updated DERBY-5630:
--------------------------------------

    Attachment: DERBY-5630.diff_try1

I think the best way to address this intermittent test failure is by converting the test to
junit so we have better control.

I'm attaching a first patch that tries to do this - this test passes as is...

However, if I change the method that looks for the 'WAIT' lock to look for something non-existent,
(for example 'WAT'), the test hangs, I believe on teardown, trying to get a lock, so I think
one of the threads is hung up, and that would not work well with other tests following.

I'll look at it some more tomorrow, if anyone has time to review and maybe spot where I'm
off, I'd appreciate it.

> 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.3.0, 10.10.1.4
>         Environment: Windows 2008, ibm 1.6 SR9 FP1, ibm 1.4.2.
>            Reporter: Myrna van Lunteren
>              Labels: derby_triage10_10
>         Attachments: DERBY-5630.diff_try1
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message