db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1958) improve XSDG3 error to print container, actual i/o operation, and file name.
Date Sat, 03 Jul 2010 20:13:49 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884964#action_12884964

Knut Anders Hatlen commented on DERBY-1958:

RAFContainer is still used on J2ME, since java.nio.* is not part of
the CDC Foundation Profile.

I think RAFContainer4 can end up throwing this exception too, since it
inherits many methods from RAFContainer, and some of the overridden
methods also call methods in the super-class. One example is the stack
trace in DERBY-3688, where RAFContainer4.openContainer() calls
RAFContainer.openContainer() and ends up raising this error.

It may be difficult to predict exactly which SQL statements end up
calling readPage() and writePage() because of the page cache. If the
database is small, you'll probably only see calls to readPage() when
you access data for the first time. writePage() should normally only
be called during checkpoint/shutdown, when a page is evicted from the
cache to give room for another page, or when a new page is created.

> improve XSDG3 error to print container, actual i/o operation, and file name.
> ----------------------------------------------------------------------------
>                 Key: DERBY-1958
>                 URL: https://issues.apache.org/jira/browse/DERBY-1958
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions:,,
>            Reporter: Mike Matrigali
>            Priority: Trivial
> The current error does not give enough information to know what container is the problem:
> ERROR XSDG3: Meta-data for Container
> org.apache.derby.impl.store.raw.data.RAFContainer@10632cd could not be
> accessed 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message