[jacorb-developer] org.omg.CORBA.CODESET_INCOMPATIBLE linux UTF-8 connecting to ISO8859_1 IOR on LInux
Seltzer, John I (John)
john.seltzer at verizon.com
Wed Mar 27 16:22:32 CET 2013
We are migrating our application to Linux.
I'm using this version of jacorb:
JacORB: 2.3.0, 17-Feb-2007
java -Dorg.omg.CORBA.ORBClass=org.jacorb.orb.ORB -Dorg.omg.CORBA.ORBSingletonClass=org.jacorb.orb.ORBSingleton org.jacorb.orb.giop.CodeSet
Operating system name: Linux
Operating system version: 2.6.39-200.24.1.el6uek.x86_64
Operating system architecture: amd64
User region: null
JVM: 1.5.0_22-b03
JacORB: 2.3.0, 17-Feb-2007
System file encoding property: UTF-8
Cannonical encoding: UTF8
Default WChar encoding: UTF16
Environment shows this:
LANG=en_US.UTF-8
I am failing when trying to invoke an idl interface whose IOR profile has this information:
TAG_INTERNET_IOP Profiles:
Profile Id: 0
IIOP Version: 1.2
-- Found 2 Tagged Components--
Unknown tag : 1447645955
#1: TAG_CODE_SETS
ForChar native code set Id: ISO8859_1
Char Conversion Code Sets:
ForWChar native code set Id: UTF16
I have tried to add these -D settings to my java command line:
-Dorg.omg.PortableInterceptor.ORBInitializerClass.standard_init=org.jacorb.orb.standardInterceptors.IORInterceptorInitializer -Djacorb.native_char_codeset=UTF-8 -Djacorb.native_wchar_codeset=UTF16
I have also tried setting native_char_codeset to en_US.UTF-8 and ISO8859_1
None of these approaches has worked. I keep getting this exception:
org.omg.CORBA.CODESET_INCOMPATIBLE: WARNING: CodeSet negotiation failed! No matching normal CodeSet found vmcid: 0x0 minor code: 0 completed: No
I have looked at various bugzilla postings on the jacorb buglist and the closest that I found was in bug 766:
------- Comment #10<http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=766#c10> From Nick Cross<mailto:rnc at prismtechnologies.com> 2009-10-26 14:08:19 [reply<http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=766#add_comment>] -------
native_char/wchar are now configurable.
Well, noting that Nick made the fix on 2009, and we are using JacORB: 2.3.0, 17-Feb-2007, that implies we need an upgrade.
I had responded in comment #10 asking which version we needed to get to obtain this fix, but never got an answer.
If readers think that we just need an upgrade, please respond with the version that we need to get or a workaround that can be used in 2.3.0 from 17 Feb 2007 or how to get a patch for this specific problem.
Otherwise please provide comments on what we could be doing wrong.
More information about the jacorb-developer
mailing list