db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1958) improve XSDG3 error to print container, actual i/o operation, and file name.
Date Thu, 19 Aug 2010 14:37:16 GMT

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

Bryan Pendleton commented on DERBY-1958:

Hi Eranda,

I don't think we can commit the current Derby-1958.diff, because it changes
messages.xml to add new arguments, but it does not change the users of
the XSDG3 message to pass the new arguments.

In addition to the changes to messages.xml and ErrorCodeTest.java, the
patch needs to ALSO modify InputStreamContainer.java and RAFContainer.java
to pass the getIdentity(), type, and file arguments when the XSDG3 message
(which is called FILE_CONTAINER_EXCEPTION in the code) is thrown.

I think the patch should contain about 7 modified calls to newException()
in those two source files.

> 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
>            Assignee: Eranda Sooriyabandara
>            Priority: Trivial
>         Attachments: Derby-1958.diff, Derby-1958.diff, reproduce.diff
> 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