[
https://issues.apache.org/jira/browse/DERBY-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-5450:
----------------------------------
Issue & fix info: High Value Fix
Urgency: Urgent
Bug behavior facts: Crash,Data corruption
Labels: derby_triage10_9 (was: )
10.9 bug triage. Without a reproducible case this is going to be hard to fix,
but would be worth looking through the data and log for clues.
There is at least one known issue that looks similar that I will link to the
issue.
> in nstest: XSLA6: Cannot recover from database & and 40XT4 errors in nstest
> (sane jars) after ASSERT FAILED
> org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED
> inconsistency in space management during insert
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5450
> URL: https://issues.apache.org/jira/browse/DERBY-5450
> Project: Derby
> Issue Type: Bug
> Components: Store, Test
> Affects Versions: 10.8.2.2
> Environment: SUSE Linux 10, ibm 1.6 SR9 FP1. 2 CPU machine, but
> hyperthreading on
> Reporter: Myrna van Lunteren
> Labels: derby_triage10_9
> Attachments: d5450_derbylog.jar
>
>
> With the 10.8 (10.8.2.2) tree sync-ed up to revision: 1179754, I ran NsTest
> Embedded with sane jars, but no derby.properties file.
> I saw the following AssertFailure:
> org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED
> inconsistency in space management during insert: slot = 146
> getSlotOffset(slot) = 3206 dataWritten = 19 freeSpace = -15 firstFreeByte =
> 3149 page = ---------------------------------------------------
> page id: Page(378,Container(0, 1153)) Overflow: false PageVersion: 895
> SlotsInUse: 159 DeletedRowCount: 93 PageStatus: 1 NextId: 317 firstFreeByte:
> 3149 freeSpace: -15 totalSpace: 4028 spareSpace: 0% minimumRecordSize : 1
> PageSize: 4096
> This was followed by:
> ------------ BEGIN SHUTDOWN ERROR STACK -------------
> ERROR XSLA6: Cannot recover the database.
> and somewhat later:
> ERROR 40XT4: An attempt was made to close a transaction that was still
> active. The transaction has been aborted.
> But after a while we get back to the errors always seen with this test (ERROR
> 22003 and XBM06).
> I will attach the derby.log, in case someone likes to look at puzzling
> behavior.
--
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
