You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (Resolved) (JIRA)" <ji...@apache.org> on 2012/04/12 00:37:17 UTC
[jira] [Resolved] (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
[ https://issues.apache.org/jira/browse/DERBY-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren resolved DERBY-5661.
---------------------------------------
Resolution: Won't Fix
I ran the nstest in a smaller configuration against trunk after the backing out of the original fix for DERBY-4437, (see DERBY-5687, revision 1311285) and where before out of 10 runs I would see 5 or so with this message, I did not see this again.
So I believe this is no longer an issue.
Marking as won't fix, because we backed out the code that caused this.
> 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
> Priority: Critical
> 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