[DERBY-5599] readlocks.sql fails with extra locks.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.8.3.0
• Fix Version/s: 10.5.3.2, 10.6.2.2, 10.7.1.4, 10.8.3.0, 10.9.1.0
• Component/s: Test
• Labels: derby_triage10_9
• Urgency: Normal
• Issue & fix info: High Value Fix
• Bug behavior facts: Regression Test Failure
• Assignee: Mike Matrigali
• Reporter: Katherine Marsden
• Created: 03/Feb/12 16:27
• Updated: 03/Sep/14 08:31
• Resolved: 21/Feb/12 18:43

Description

I saw this failure for the Feb 1 run at:
http://people.apache.org/~myrnavl/derby_test_results/v10_8/linux/testlog/ibm15/1239442-derbyall_diff.txt

I think it is likely the index statistics update kicking in during the test. I am thinking should not be disabled for the derbyall store tests as having it kick in can cause upredictable reporting of locks pages used, etc.

• • • Start: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:11:01 ***
      11113a11114
      > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
      11122a11124
      > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
      11131a11134
      > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
      11138a11142
      > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
      Test Failed.
    • End: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:13:31 ***

Issue Links

• is duplicated by: DERBY-2947 Reoccurrence of DERBY-861: Intermittent failure of store/readlocks.sql
• relates to: DERBY-2947 Reoccurrence of DERBY-861: Intermittent failure of store/readlocks.sql