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] Updated: (DERBY-1958) improve XSDG3 error to print container, actual i/o operation, and file name.
Date Sat, 21 Aug 2010 21:09:16 GMT

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

Bryan Pendleton updated DERBY-1958:
-----------------------------------

    Attachment: reviewedPatch.diff

Hi Eranda,

I took your patch and made some additional changes, and have attached
the revised patch as 'reviewedPatch.diff'.

It would be great if you could have a look and proof-read the updated patch.

The regression tests run clean for me with this patch.

I also planted fake IOExceptions into the code in a couple cases
and verified that the message is printed cleanly to derby.log.

Let me know if you see anything else that we need to attend to
prior to committing this patch.

Thanks!


> 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: 10.1.3.1, 10.2.1.6, 10.3.1.4
>            Reporter: Mike Matrigali
>            Assignee: Eranda Sooriyabandara
>            Priority: Trivial
>         Attachments: Derby-1958.diff, Derby-1958.diff, Derby-1958.diff, reproduce.diff,
reviewedPatch.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.


Mime
View raw message