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 Sun, 15 Aug 2010 22:06:16 GMT

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

Bryan Pendleton commented on DERBY-1958:

I think that the changes to messages.xml and ErrorCodeTest.java look fine.

I think what we need is a patch which includes the changes to messages.xml and
ErrorCodeTest.java, and also includes changes to InputStreamContainer.java and
RAFContainer.java which adjust all of the places where FILE_CONTAINER_EXCEPTION
is generated, to use the new invocation

       throw StandardException.newException(SQLState.FILE_CONTAINER_EXCEPTION, 
                                       new Object[] {getIdentity().toString(),type,file})

I don't think we need the 'reproduction' changes to BaseDataFileFactoryJ4.java,
nor the "if(pageNumber>1)" section in RAFContainer, in the final patch, as those
were just present to enable you to verify the proper formatting of the error message.

Does that make sense?

> 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