db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6504) change AllocPage.ReadContainerInfo to catch ArrayIndexOutOfBoundsException and turn it into Derby error.
Date Thu, 05 Jun 2014 18:35:02 GMT

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

ASF subversion and git services commented on DERBY-6504:
--------------------------------------------------------

Commit 1600721 from [~myrna] in branch 'code/trunk'
[ https://svn.apache.org/r1600721 ]

DERBY-6504; change AllocPage.ReadContainerInfo to catch ArrayIndexOutOfBoundsException and
turn it into Derby error.
   Adjusting lang/ErrorCodeTest to reflect the new message.

> change AllocPage.ReadContainerInfo to catch ArrayIndexOutOfBoundsException and turn it
into Derby error.
> --------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6504
>                 URL: https://issues.apache.org/jira/browse/DERBY-6504
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.6.1.0, 10.8.2.2
>            Reporter: Mike Matrigali
>            Assignee: Myrna van Lunteren
>         Attachments: DERBY-6504.diff, DERBY-6504_3.diff, DERBY-6504_errorcodetst.diff,
derby.logtry1, derby.logtry2, derby.logtry4
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message