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 "Suresh Thalamati (JIRA)" <de...@db.apache.org> on 2005/12/14 01:38:45 UTC
[jira] Created: (DERBY-758) CachedPage.readPage() can loop forever on insane builds if the read from the container keep failing with IO Exceptions.
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 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
Re: [jira] Created: (DERBY-758) CachedPage.readPage() can loop forever
on insane builds if the read from the container keep failing with IO
Exceptions.
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
Myrna van Lunteren <m....@gmail.com> writes:
> On 12/15/05, Knut Anders Hatlen <Kn...@sun.com> wrote:
>>
>> "Suresh Thalamati (JIRA)" <de...@db.apache.org> writes:
[...]
>> > 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?
>>
> Out of curiosity - if you can reproduce this at will - can you also
> reproduce it with the jit switched off?
Yes, same problem with -Xnojit. You can reproduce it with the test
case I recently attached to DERBY-733.
--
Knut Anders
Re: [jira] Created: (DERBY-758) CachedPage.readPage() can loop forever on insane builds if the read from the container keep failing with IO Exceptions.
Posted by Myrna van Lunteren <m....@gmail.com>.
On 12/15/05, Knut Anders Hatlen <Kn...@sun.com> wrote:
>
> "Suresh Thalamati (JIRA)" <de...@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
>
>
Out of curiosity - if you can reproduce this at will - can you also
reproduce it with the jit switched off?
Myrna
Re: [jira] Created: (DERBY-758) CachedPage.readPage() can loop forever
on insane builds if the read from the container keep failing with IO
Exceptions.
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
"Suresh Thalamati (JIRA)" <de...@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
[jira] Assigned: (DERBY-758) CachedPage.readPage() can loop forever on insane builds if the read from the container keep failing with IO Exceptions.
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-758?page=all ]
Mike Matrigali reassigned DERBY-758:
------------------------------------
Assign To: Mike Matrigali
> 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
>
> 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
[jira] Resolved: (DERBY-758) CachedPage.readPage() can loop forever on insane builds if the read from the container keep failing with IO Exceptions.
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Closed: (DERBY-758) CachedPage.readPage() can loop forever
on insane builds if the read from the container keep failing with IO
Exceptions.
Posted by "Suresh Thalamati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-758?page=all ]
Suresh Thalamati closed DERBY-758:
----------------------------------
> 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, 10.1.3.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
[jira] Updated: (DERBY-758) CachedPage.readPage() can loop forever
on insane builds if the read from the container keep failing with IO
Exceptions.
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-758?page=all ]
Mike Matrigali updated DERBY-758:
---------------------------------
Fix Version: 10.1.3.0
back porting change targeted for 10.1.3 release.
m101_142:31>svn commit
Sending java\engine\org\apache\derby\impl\store\raw\data\CachedPage.java
Transmitting file data .
Committed revision 394767.
> 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, 10.1.3.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