db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (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 Thu, 15 Mar 2012 23:54:37 GMT
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


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