[
https://issues.apache.org/jira/browse/DERBY-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898664#action_12898664
]
Eranda Sooriyabandara commented on DERBY-1958:
----------------------------------------------
Hi Bryan,
I throw exception,
throw StandardException.newException(SQLState.FILE_CONTAINER_EXCEPTION, new
Object[] {getIdentity().toString(),type,file})
and the message format of the XSDG3 error as,
Meta-data for {0} could not be accessed to {1} {2} in message.xml
and got the exception error message as
ERROR XSDG3: Meta-data for Container(0, 161) could not be accessed to read
/home/eranda/Desktop/DERBY/Derby-1958/trunk/test/MyDB/seg0/ca1.dat
Is it good enough for now?
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
> Priority: Trivial
> Attachments: Derby-1958.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.rafcontai...@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.
