[DERBY-6504] change AllocPage.ReadContainerInfo to catch ArrayIndexOutOfBoundsException and turn it into Derby error.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.6.1.0, 10.8.2.2
• Fix Version/s: 10.10.2.1, 10.11.1.1
• Component/s: Store
• Issue & fix info: High Value Fix
• Assignee: Myrna van Lunteren
• Reporter: Mike Matrigali
• Created: 10/Mar/14 23:54
• Updated: 09/Sep/16 09:51
• Resolved: 06/Jun/14 20:07

Description

Users have reported databases that will not boot with stack traces showing:
Caused by: java.lang.ArrayIndexOutOfBoundsException
at java.lang.System.arraycopy(Native Method)
at org.apache.derby.impl.store.raw.data.AllocPage.ReadContainerInfo(Unknown Source)
at org.apache.derby.impl.store.raw.data.FileContainer.readHeader(Unknown Source)

I suggest the code be changed to catch the out of bounds and turn it
into a StandardException and include as much runtime information as
possible so that the underlying problem can be diagnosed. Information
should include sizes of both arrays, the amount of data being copied ("N"),
and possibly a hex dump of the source array.

Issue Links

• is related to: DERBY-5936 AllocPage.ReadContainerInfo throws ArrayIndexOutOfBoundsException at arraycopy
• relates to: DERBY-6606 ErrorCodeTest AssertionFailedError: Unexpected row count, expected: 174, actual: 175