[
https://issues.apache.org/jira/browse/DERBY-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574948#action_12574948
]
Knut Anders Hatlen commented on DERBY-3487:
-------------------------------------------
Does the test harness report this as "timed out trying to kill all testers"?
I'm not sure if it's related, but in the testing of release candidates for
10.3.1 and 10.3.2, stress.multi failed with that message on some platforms.
That's the same message as we see in many of Henri's nightly tests now. In the
reports from the release testing, these failures were (incorrectly?) identified
as DERBY-1750.
The failure is mentioned in these test reports:
http://dbtg.thresher.com/derby/test/10.3.2.1_RC/TestReport.html
http://dbtg.thresher.com/derby/test/10.3.1.4_RC/TestReport.html
http://dbtg.thresher.com/derby/test/10.3.1.1_RC/TestReport.html
http://dbtg.thresher.com/derby/test/10.3.1.0_RC/TestReport.html
> 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.
