[DERBY-5039] store/updatelocksJDBC30.sql test failing in tinderbox when background update statistics are enabled.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.8.1.2
• Component/s: Test
• Bug behavior facts: Regression, Regression Test Failure
• Assignee: Mike Matrigali
• Reporter: Mike Matrigali
• Created: 14/Feb/11 18:14
• Updated: 17/Jun/13 09:19
• Resolved: 23/Feb/11 17:17

Description

updatelocksJDBC30 is failing consistently in tinderbox since checkin 1069598 for DERBY-4939: Enable istat daemon and tests. This is probably same issue as DERBY-5038, and if test changes are required similar changes will be needed for this test. Should concentrate on resolving DERBY-5038 first.

http://dbtg.foundry.sun.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/1069717-derbyall_diff.txt

Failure Details:

• • • • • • • • • Diff file derbyall/storeall/storemats/storemats/updatelocksJDBC30.diff
    • Start: updatelocksJDBC30 jdk1.6.0_18 storemats:storemats 2011-02-11 11:20:56 ***
      14874,14883d14873
      < APP |UserTran|TABLE |1 |IX |A |Tablelock |GRANT|ACTIVE
      < ij> next scan_cursor;
      < A |B |C
      < --------------------------------------------------------------------------------------------------------------------------------------------------------
      < 3 |-30 |-three
      < ij> update a set b=30,c='three' where current of scan_cursor;
      < 1 row inserted/updated/deleted
      < ij> select * from lock_table order by tabname, type desc, mode, cnt, lockname;
      < USERNAME|TRANTYPE|TYPE |CNT |MODE|TABNAME |LOCKNAME |STATE|STATUS
      < ---------------------------------------------------------------------------
      14884a14875,14884
      > ij> next scan_cursor;
      > A |B |C
      > --------------------------------------------------------------------------------------------------------------------------------------------------------
      > 3 |-30 |-three
      > ij> update a set b=30,c='three' where current of scan_cursor;
      > 1 row inserted/updated/deleted
      > ij> select * from lock_table order by tabname, type desc, mode, cnt, lockname;
      > USERNAME|TRANTYPE|TYPE |CNT |MODE|TABNAME |LOCKNAME |STATE|STATUS
      > ---------------------------------------------------------------------------
      > APP |UserTran|TABLE |3 |IX |A |Tablelock |GRANT|ACTIVE
      14895 del
      < APP |UserTran|TABLE |2 |IX |A |Tablelock |GRANT|ACTIVE
      14895a14895
      > APP |UserTran|TABLE |3 |IX |A |Tablelock |GRANT|ACTIVE
      14905 del
      < APP |UserTran|TABLE |2 |IX |A |Tablelock |GRANT|ACTIVE
      14905a14905
      > APP |UserTran|TABLE |3 |IX |A |Tablelock |GRANT|ACTIVE
      Test Failed.
    • End: updatelocksJDBC30 jdk1.6.0_18 storemats:storemats 2011-02-11 11:21:03 ***

Issue Links

• is broken by: DERBY-4939 Enable istat daemon and tests
• is related to: DERBY-5038 updatelocks test failing in tinderbox when background update statistics are enabled.
• requires: DERBY-4090 Provide the ability to run tests concurrently on the same machine