You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mike Matrigali (JIRA)" <ji...@apache.org> on 2006/11/17 17:10:38 UTC
[jira] Updated: (DERBY-2093) Error in initSlotTable() can cause NPE
or ASSERT rather than reporting page number in corrupt page message.
[ http://issues.apache.org/jira/browse/DERBY-2093?page=all ]
Mike Matrigali updated DERBY-2093:
----------------------------------
committed to trunk:
m1_ibm142:18>svn commit
Sending java\engine\org\apache\derby\impl\store\raw\data\StoredPage.java
Transmitting file data .
Committed revision 476190.
> Error in initSlotTable() can cause NPE or ASSERT rather than reporting page number in corrupt page message.
> -----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2093
> URL: http://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.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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira