db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-758) CachedPage.readPage() can loop forever on insane builds if the read from the container keep failing with IO Exceptions.
Date Thu, 15 Dec 2005 22:28:46 GMT
     [ http://issues.apache.org/jira/browse/DERBY-758?page=all ]
     
Mike Matrigali resolved DERBY-758:
----------------------------------

    Fix Version: 10.2.0.0
     Resolution: Fixed

DERBY-758, fixing I/O retry logic to throw an I/O exception rather
than loop forever on I/O read errors.  4 retry's are attempted before
giving up.

committed as svn 357083

> CachedPage.readPage() can loop forever on insane builds if  the read from the container
keep failing with  IO Exceptions.
> -------------------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-758
>          URL: http://issues.apache.org/jira/browse/DERBY-758
>      Project: Derby
>         Type: Bug
>   Components: Store
>     Reporter: Suresh Thalamati
>     Assignee: Mike Matrigali
>      Fix For: 10.2.0.0

>
> org.apache.derby.impl.store.raw.data.CachedPage.readPage() loops forever  if  read  from
the container 
> keeps failing  with an  IOException.  On debug build it marks the system as corrupt ,
but in non-debug builds
> it just keeps retrying to read the page from the disk. 
> I think that is not good,  if a disk fails for some reason when attempting to read a
page;   Derby will just 
> hog the cpu and user will not know why. 
>  

-- 
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