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

Kathey Marsden commented on DERBY-3487:
---------------------------------------

Yes the test harness reports this as timed out waiting for testers.  
I ran the test 50 times and saw two types of failures, both 
complaining that the test had timed out waiting for testers.
The other is described here:
http://www.nabble.com/Another-kind-of-stress.multi-failiure-to15781682.html#a15787740

which may be an issue with the statement cache.  I will file a bug today.

I haven't seen any matching DERBY-1750, but Ole said he has.

Kathey



> stress.multi fails with org.apache.derby.shared.common.sanity.AssertFailure: 
> ASSERT FAILED No page at pagenumber: 6; ContainerHandle = 
> BaseContainerHandle:(Container(0, 65))
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3487
>                 URL: https://issues.apache.org/jira/browse/DERBY-3487
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure, Store
>    Affects Versions: 10.4.0.0
>            Reporter: Kathey Marsden
>            Priority: Critical
>         Attachments: derbylog.zip
>
>
> Running stress.multi on Linux IBM 1.5  the test failed with the following 
> trace in the derby.log:
> select * from main2 :End prepared statement
> 2008-03-01 04:31:39.460 GMT Thread[Thread-4,5,workers] (XID = 149271), 
> (SESSIONID = 12253), (DATABASE = mydb), (DRDAID = null), Committing
> Exception trace: 
> org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED No page at 
> pagenumber: 6; ContainerHandle = BaseContainerHandle:(Container(0, 65))
>       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.store.access.btree.ControlRow.get(ControlRow.java:838)
>       at 
> org.apache.derby.impl.store.access.btree.ControlRow.get(ControlRow.java:820)
>       at 
> org.apache.derby.impl.store.access.btree.BTreePostCommit.purgeRowLevelCommittedDeletes(BTreePostCommit.java:462)
>       at 
> org.apache.derby.impl.store.access.btree.BTreePostCommit.performWork(BTreePostCommit.java:278)
>       at 
> org.apache.derby.impl.services.daemon.BasicDaemon.serviceClient(BasicDaemon.java:331)
>       at 
> org.apache.derby.impl.services.daemon.BasicDaemon.work(BasicDaemon.java:668)
>       at 
> org.apache.derby.impl.services.daemon.BasicDaemon.run(BasicDaemon.java:394)
>       at java.lang.Thread.run(Thread.java:803)
> 2008-03-01 04:31:39.515 GMT Thread[derby.rawStoreDaemon,5,derby.daemons] 
> Cleanup action starting
> org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED No page at 
> pagenumber: 6; ContainerHandle = BaseContainerHandle:(Container(0, 65))
>       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.store.access.btree.ControlRow.get(ControlRow.java:838)
>       at 
> org.apache.derby.impl.store.access.btree.ControlRow.get(ControlRow.java:820)
>       at 
> org.apache.derby.impl.store.access.btree.BTreePostCommit.purgeRowLevelCommittedDeletes(BTreePostCommit.java:462)
>       at 
> org.apache.derby.impl.store.access.btree.BTreePostCommit.performWork(BTreePostCommit.java:278)
>       at 
> org.apache.derby.impl.services.daemon.BasicDaemon.serviceClient(BasicDaemon.java:331)
>       at 
> org.apache.derby.impl.services.daemon.BasicDaemon.work(BasicDaemon.java:668)
>       at 
> org.apache.derby.impl.services.daemon.BasicDaemon.run(BasicDaemon.java:394)
>       at java.lang.Thread.run(Thread.java:803)
> Cleanup action completed

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to