[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

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Invalid
• Affects Version/s: 10.9.1.0
• Environment: windows XP with ibm 1.6 sr9
• Bug behavior facts: Regression Test Failure
• Assignee: Unassigned
• Reporter: Myrna van Lunteren
• Created: 15/Mar/12 23:52
• Updated: 17/Jun/13 09:19
• Resolved: 11/Apr/12 22:57

Description

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)

Issue Links

• is related to: DERBY-5422 IndexOutOfBoundsException followed by NullPointerException in cleanup during system.nstest
• is related to: DERBY-5428 ns test error: ERROR 38000: The exception 'org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED Identity being changed on a live cacheable. Old uuidString = 846c00a0-0132-88d8-fec0-000000080920' was thrown while evaluating an expression