[DERBY-5450] 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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 10.8.2.2
• Component/s: Store, Test
• Labels: derby_triage10_9
• Environment: SUSE Linux 10, ibm 1.6 SR9 FP1. 2 CPU machine, but hyperthreading on
• Urgency: Urgent
• Issue & fix info: High Value Fix
• Bug behavior facts: Crash, Data corruption
• Assignee: Unassigned
• Reporter: Myrna van Lunteren
• Created: 08/Oct/11 01:54
• Updated: 19/Apr/12 04:20
• Resolved: 19/Apr/12 04:20

Description

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.

Issue Links

• relates to: DERBY-4923 update of a long row can fail with ERROR nospc: nospc.U exception.