On 13-11-2014 19:14, Mark Rotteveel mark@... [Firebird-Java]
wrote:

> On 13-11-2014 16:21, hugo.larson@... [Firebird-Java] wrote:
>> I get this exception when setting the character set as advised with
>> Excelsion JET jvm.
>> Tried with both WIN1252 and ISO8859_1.
>>
>> BR,
>> Hugo.
>>
>> java.nio.charset.UnsupportedCharsetException: EUC_JP
>> at java.nio.charset.Charset.<unknown>(Unknown Source)
>> at
>> org.firebirdsql.encodings.EncodingFactory.loadEncodings(Unknown Source)
>> at
>> org.firebirdsql.encodings.EncodingFactory.getJavaEncoding(Unknown Source)
>> at
>> org.firebirdsql.jdbc.FBDriverPropertyManager.<unknown>(Unknown Source)
>> at
>> org.firebirdsql.jdbc.FBDriverPropertyManager.normalize(Unknown Source)
>> at org.firebirdsql.jdbc.AbstractDriver.connect(Unknown Source)
>
> It looks like Excelsior doesn't know some of the character sets that are
> supported by Oracle Java, and Jaybird doesn't handle this case well.
>
> The workaround is to edit the isc_encodings.properties and comment out
> (by adding a #) the character sets you don't need or that are not
> supported (eg change the line "EUCJ_0208 EUC_JP" to "#EUCJ_0208 EUC_JP").
>
> You might also want to check if Excelsior has an extension library for
> character sets (eg i18n.jar (like old Java versions had) or charsets.jar
> (like current Java versions)).

I created ticket http://tracker.firebirdsql.org/browse/JDBC-371 to fix
this for Jaybird 2.2.6.

Mark
--
Mark Rotteveel