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 Fri, 16 Mar 2012 00:06:49 GMT

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

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

The run4 results were obtained by running the test like so:
java -Dderby.nstest.backupRestore=false org.apache.derbyTesting.system.nstest.NsTest Embedded
small > nstest.out_run4_nobackup 2>&1
derby.log was then renamed.
The run5 results were obtained by running the test like so:
java org.apache.derbyTesting.system.nstest.NsTest Embedded small > nstest.out_run5_wbackup
2>&1

To enable the run with small configuration one must be sync-ed up to revision 1300658 for
trunk.
I've made some small improvements to running with -Dderby.nstest.backupRestore=false which
were not committed at the time I ran this test, but they're committed now with revision 1301290
(trunk).


I have tried to run the test on a linux machine too but saw no failures there. 
                
> 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