db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3780) Run junit tests with -Dfile.encoding="UTF-16" to expose encoding issues and analyze failures
Date Fri, 18 Jul 2008 09:32:31 GMT

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

Knut Anders Hatlen commented on DERBY-3780:

I haven't studied the results in detail, I just wanted to add that the file.encoding property
is not a standard property, and it is meant to be a read-only property that tells you the
default encoding. Since you're not supposed to change the property, some parts of the class
library may use it to determine the default encoding, whereas others may use another way to
find it. So some of the failures may be caused by the class library being confused and using
the encoding inconsistently.

Seems like you also ran out of perm gen space. Possibly because UTF-16 requires more space
in many cases?

> Run junit tests with -Dfile.encoding="UTF-16" to expose encoding issues and analyze failures
> --------------------------------------------------------------------------------------------
>                 Key: DERBY-3780
>                 URL: https://issues.apache.org/jira/browse/DERBY-3780
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions:
>            Reporter: Kathey Marsden
>            Priority: Minor
>         Attachments: ReadEncodedFile.java, suites_all_utf16.txt
> Wth sun jkd 1.5 and 1.6 you can run JUnit tests with -Dfile.encoding="UTF-16" to help
expose encoding issues with Derby and tests.    Run suites.All and analyze failures.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message