db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <Knut.Hat...@Sun.COM>
Subject Re: [jira] Created: (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 10:51:41 GMT
"Suresh Thalamati (JIRA)" <derby-dev@db.apache.org> writes:

> 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
>
>
> 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 saw this problem when I tested IBM's new 1.5 JVM on Linux. For some
reason, the VM starts throwing IOExceptions when I try to access a
relatively large table:

java.io.IOException: Invalid argument
        at java.io.RandomAccessFile.seek(Native Method)
        at org.apache.derby.impl.store.raw.data.RAFContainer.readPage(RAFContainer.java:198)
        ....

In insane mode Derby just loops forever without printing any messages,
as Suresh described.

I do not see this problem on Sun JVM 1.4.2/1.5.0 or IBM JVM
1.4.2. Does anyone know why I get the exception on that platform?

-- 
Knut Anders


Mime
View raw message