db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-4211) 'derbyall/encryptionAll/storemats.fail:store/updatelocksJDBC30.sql' fails with unexpected locks
Date Thu, 26 May 2011 10:27:47 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039628#comment-13039628
] 

Kristian Waagan commented on DERBY-4211:
----------------------------------------

Running store/updatelocksJDBC30.sql with istat logging indicates that no istat work is being
done:
Thu May 26 12:10:53 CEST 2011 Thread[main,5,main] {istat} stopping daemon, active=false, work/age=0/8338
[q/p/s=0/0/0,err:k/u/c=0/0/0,rej:f/d/o=0/0/0]

There have been reports of failures for these tests long before the istat feature was available.
Even though the initial addition of the istat feature caused failures for at least some of
the updatelocks tests, this doesn't appear to be the case any more.

One theory is that some times locks are taken due to activity in a background thread. Would
rewriting the tests to JUnit and adding wait/retry logic wrt querying the lock table be a
way forward?
A quick look at the existing test classes suggests that this is a fair amount of work, but
the tests seem to rely on a rather smallish set of core functions.

> 'derbyall/encryptionAll/storemats.fail:store/updatelocksJDBC30.sql' fails with unexpected
locks
> -----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4211
>                 URL: https://issues.apache.org/jira/browse/DERBY-4211
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.6.1.0
>         Environment: OS:
> Solaris 10 5/08 s10x_u5wos_10 X86 64bits - SunOS 5.10 Generic_127128-11
> JVM:
> Sun Microsystems Inc.
> java version "1.6.0_06"
> Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
> Java HotSpot(TM) Client VM (build 10.0-b22, mixed mode)
>            Reporter: Ole Solberg
>            Assignee: Mike Matrigali
>             Fix For: 10.5.3.1, 10.6.2.1, 10.7.1.1
>
>
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/771180-derbyall_diff.txt
> ********* Diff file derbyall/encryptionAll/storemats/storemats/updatelocksJDBC30.diff
> *** Start: updatelocksJDBC30 jdk1.6.0_06 storemats:storemats 2009-05-04 11:56:42 ***
> 9184a9185
> > APP     |UserTran|ROW     |1   |U   |A           |(2,6)     |GRANT|ACTIVE  
> 9194a9196
> > APP     |UserTran|ROW     |1   |U   |A           |(2,6)     |GRANT|ACTIVE  
> 9205a9208
> > APP     |UserTran|ROW     |1   |U   |A           |(2,6)     |GRANT|ACTIVE  
> 9215a9219
> > APP     |UserTran|ROW     |1   |U   |A           |(2,6)     |GRANT|ACTIVE  
> 9224a9229
> > APP     |UserTran|ROW     |1   |U   |A           |(2,6)     |GRANT|ACTIVE  
> Test Failed.
> *** End:   updatelocksJDBC30 jdk1.6.0_06 storemats:storemats 2009-05-04 11:57:00 ***

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message