Derby
  1. Derby
  2. DERBY-5630

intermittent test failure in store/lockTableVTI.sql

    Details

    • Urgency:
      Normal
    • Issue & fix info:
      Patch Available
    • Bug behavior facts:
      Regression Test Failure

      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

      1. DERBY-5630.diff2
        18 kB
        Myrna van Lunteren
      2. DERBY-5630.diff_try1
        11 kB
        Myrna van Lunteren

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Myrna van Lunteren
              Reporter:
              Myrna van Lunteren
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development