db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2093) Error in initSlotTable() can cause NPE or ASSERT rather than reporting page number in corrupt page message.
Date Fri, 17 Nov 2006 16:10:40 GMT
     [ http://issues.apache.org/jira/browse/DERBY-2093?page=all ]

Mike Matrigali updated DERBY-2093:
----------------------------------

    Fix Version/s: 10.3.0.0

> 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

        

Mime
View raw message