You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mike Matrigali (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/21 19:43:46 UTC
[jira] [Resolved] (DERBY-5599) readlocks.sql fails with extra
locks.
[ https://issues.apache.org/jira/browse/DERBY-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali resolved DERBY-5599.
-----------------------------------
Resolution: Fixed
Fix Version/s: 10.9.0.0
10.8.2.3
10.7.1.4
10.6.2.2
10.5.3.2
> readlocks.sql fails with extra locks.
> -------------------------------------
>
> Key: DERBY-5599
> URL: https://issues.apache.org/jira/browse/DERBY-5599
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.8.2.3
> Reporter: Kathey Marsden
> Assignee: Mike Matrigali
> Labels: derby_triage10_9
> Fix For: 10.5.3.2, 10.6.2.2, 10.7.1.4, 10.8.2.3, 10.9.0.0
>
>
> 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 ***
--
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