[
https://issues.apache.org/jira/browse/DERBY-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali resolved DERBY-2093.
-----------------------------------
Resolution: Fixed
Fix Version/s: 10.2.3.0
> Error in initSlotTable() can cause NPE or ASSERT rather than reporting page
> number in corrupt page message.
> -----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2093
> URL: https://issues.apache.org/jira/browse/DERBY-2093
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.2.1.6
> Reporter: Mike Matrigali
> Assigned To: Mike Matrigali
> Priority: Minor
> Fix For: 10.2.3.0, 10.3.0.0
>
>
> Error in initSlotTable() can cause NPE or ASSERT rather than reporting page
> number in corrupt page message. The problem is
> that depending on when the error is encountered we are in the middle of
> setting up a new page, so you can't use normal
> access routines for identifiying the page (like getIdentity() ) as they may
> not be set up yet.
> The fix is to change the error messages to use a passed in identity rather
> than counting on correct setup during initialization failure
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
