db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (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 Wed, 21 Mar 2012 00:52:39 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren updated DERBY-5661:
--------------------------------------

    Attachment: jarredderby_log6.jar
                nstest.out6

Attaching a derby.log (jarred with jar -cvfM) and nstest.out6 obtained by running the test
with trunk sane jars as follows:
java -Dderby.nstest.backupRestore=false org.apache.derbyTesting.system.nstest.NsTest Embedded
small > nstest.out6 2>&1

and with a derby.properties in the directory where I started derby with the following contents:
---------------------------------------
derby.infolog.append=true
derby.stream.errorlogSeverity=0
derby.language.logStatementText=true
#derby.language.logQueryPlan=true
derby.locks.monitor=true
derby.locks.deadlockTrace=true
#derby.locks.waitTimeout=300
#derby.locks.deadlockTimeout=300
---------------------------------------

This was on my slower 1 CPU system. The test ran into DERBY-5661, DERBY-5428, DERBY-5454,
DERBY-5430, DERBY-5422. Also a strange ArrayIndexOutOfBounds error is visible in derby.log
(renamed to derby.log6 to differentiate).

Hopefully this is helpful.

                
> 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, jarredderby_log6.jar,
nstest.out6, 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