db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4211) 'derbyall/encryptionAll/storemats.fail:store/updatelocksJDBC30.sql' fails with unexpected locks
Date Fri, 11 Feb 2011 19:07:57 GMT

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

Mike Matrigali commented on DERBY-4211:
---------------------------------------

My first guess is this test is being affected by the istats change.  I would be happy to fix
the test, but first want to make sure
there is not an istats bug that I would be hiding.  So would like some feed back on the following:

1) Are the locks that are requested in background gotten on a "user" transaction, rather than
an internal transaction?  If so, should
they be?  Current the background daemon uses internal transactions so that user's querying
the lock table can tell the difference between
their xact's and internal work.

2) I see from the derby.log that istats work is definitely happening.  Should istats be working
on these tables.  The tables in this test always about
7 rows.  From reading the ones created in the updatelocks test are always created using the
following form:
    create table a(a int, b int);
    alter table a add column c varchar(1900);
    insert into a values (1, 10, 'one');
    insert into a values (2, 20, 'two');
    insert into a values (3, 30, 'three');
    insert into a values (4, 40, 'four');
    insert into a values (5, 50, 'five');
    insert into a values (6, 60, 'six');
    insert into a values (7, 70, 'seven');
    create index a_idx on a (a);
    commit;

Some have indexes, some don't.  If they have indexes they are always created after the row
are loaded so all stats should be up to date.  


> '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