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-1958) improve XSDG3 error to print container, actual i/o operation, and file name.
Date Mon, 21 Jun 2010 17:03:26 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Mike Matrigali updated DERBY-1958:

This is an issue that "should not happen."  You can search JIRA for XSDG3 to see the reported
issues where this exception has been thrown, but I believe all the reproducible cases have
been fixed.  I reported this so that if we get another bug in the future the error at least
the error will be more descriptive.

If you are interested in fixing, I would find somewhere in the code that throws this
exception and in your private codeline change it so that the code always throws this
error so that you can hand test the error message change.  I don't know of any way
to cause this in a correctly running current system.

> 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