db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5661) ASSERT failure in nstest; Exception in thread "derby.index-stat-thread" org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED transaction not pristine
Date Tue, 20 Mar 2012 21:07:38 GMT

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

Myrna van Lunteren commented on DERBY-5661:
-------------------------------------------

Thanks for the experiments and evaluation Kristian...

I ran the nstest Embedded small configuration 10 times with ibm 1.6 SR9 FP1 with sane jars
from 10.8 branch and trunk, on the same machine (Windows XP on vmware).

With 10.8, I only saw a 40001 (like DERBY-5454) in one run, and a 40XL1 (lock timeout) in
one other run.

With trunk, I saw the following:
5 runs ok (run0, run3, run5, run6, run7)
run1: immediately following kick-off of testing (incl. backup) threads: DERBY-5661 followed
by DERBY-5428

run2: immediately following kick-off of testing (incl. backup) threads:  DERBY-5661 followed
by DERBY-5428 followed by DERBY-5661; one more occurrence of DERBY-5661, and once more, followed
by DERBY-5428

run4: DERBY-5430, followed by a 40XL1 lock timeout, followed by DERBY-5428; one more occurrence
of DERBY-5428

run8: immediately following kick-off of testing (incl. backup) threads: DERBY-5428

run9: DERBY-5661, followed by DERBY-5428.  



I also don't know what to make of this, except that there is apparently some confused state
that can have a number of different errors as a result.
                
> ASSERT failure in nstest; Exception in thread "derby.index-stat-thread" org.apache.derby.shared.common.sanity.AssertFailure:
ASSERT FAILED transaction not pristine
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5661
>                 URL: https://issues.apache.org/jira/browse/DERBY-5661
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.9.0.0
>         Environment: windows XP with ibm 1.6 sr9
>            Reporter: Myrna van Lunteren
>         Attachments: derby.log_run4_nobackup, derby.log_run5_wbackup, nstest.out_run4_nobackup,
nstest.out_run5_wbackup
>
>
> While running the small configuration of nstest with trunk/sane jars on a windows machine,
I saw this a few times (in addition to the Assert failure as described in DERBY-5428):
> Exception in thread "derby.index-stat-thread" org.apache.derby.shared.common.sanity.AssertFailure:
ASSERT FAILED transaction not pristine
> 	at org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:162)
> 	at org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:147)
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl.processingLoop(IndexStatisticsDaemonImpl.java:849)
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl.run(IndexStatisticsDaemonImpl.java:714)
> 	at java.lang.Thread.run(Thread.java:736)
> There is a print out of all threads following. I'll attach a couple of result files obtained
this way.
> One run was with the backup thread running, the other without (by adding -Dderby.nstest.backupRestore=false)

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

        

Mime
View raw message