[
https://issues.apache.org/jira/browse/DERBY-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-6157:
--------------------------------------
Attachment: DERBY-6157.diff
DERBY-6157.stat
Attaching a patch which replaces the message.
The full text was only reflected in lang/ErrorCodeTest.java, so I only ran that
test.
I removed the message from most languages.properties files, so that the English
will show up instead of the unhelpful translated one.
Except I amused myself with devising a translation for German, French, Spanish
and Italian.
I don't have the skill of a licensed translator, but with some limited
knowledge, help from various free translators, some dictionaries, and the text
of other translated messages, I think this is pretty close, better than what it
was, and presumably if we get another all-out translation contribution these
will get overwritten anyway.
> text for message XSLA4 might encouraging people to delete part of the
> transaction log
> -------------------------------------------------------------------------------------
>
> Key: DERBY-6157
> URL: https://issues.apache.org/jira/browse/DERBY-6157
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.9.2.2, 10.10.1.1, 10.10.1.2, 10.11.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-6157.diff, DERBY-6157.stat
>
>
> This is not new, but while reviewing some of the 'disk full' messages
> resulting from one of the long-running system tests, I realized that the text
> of ERROR XSLA4 could be read, by people unfamiliar with derby and brave or in
> a panic, as suggesting one to delete parts of the log directory:
> "ERROR XSLA4: Cannot write to the log, most likely the log is full. Please
> delete unnecessary files. It is also possible that the file system is read
> only, or the disk has failed, or some other problems with the media."
> We've been fighting people deleting files from the log directory, and even if
> this message text may not be the culprit, it certainly is open for
> misinterpretation.
> I think we need to change this message.
> English language experts and native as well as non-native speakers are
> particularly invited to chime in.
> One suggestion is:
> Error encountered when attempting to write the transaction recovery log.
> Most likely the disk holding the recovery log is full. If the disk is full,
> the only way to proceed is to free up space on the disk by either expanding
> it or deleting files not related to Derby. It is also possible that the file
> system and/or disk where the Derby transaction log resides is read only. The
> error can also be encountered if the disk or filesystem has failed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
