Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <13028716.6271277182614599.JavaMail.jira@thor>
Date: Tue, 22 Jun 2010 00:56:54 -0400 (EDT)
From: "Bryan Pendleton (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1958) improve XSDG3 error to print
 container, actual i/o operation, and file name.
In-Reply-To: <10088284.1160674715080.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bryan Pendleton commented on DERBY-1958:
----------------------------------------

Hi Eranda,
I did a somewhat similar private alteration to Derby for DERBY-3729,
so hopefully looking at that work will be a good place to start.

If you look through the comments and attachments to DERBY-3729,
and in particular this comment:
https://issues.apache.org/jira/browse/DERBY-3729?focusedCommentId=12829808&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12829808
I think you should be able to get some ideas about how to make a
similar modification in order to expose this XSDG3 error message.

Of course, whereas I modified CachedPage.java, you'll want to make
a modification somewhere in RAFContainer.java instead. But the basic
principles of the technique should be the same.


> 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
>            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.