|
Problem |
For an org.omg.CORBA.DATA_CONVERSION error, the WebSphere
Infocenter lists minor code possiblities of 1 to 5, but not on 6: http://www.ibm.com/software/webservers/appserv/doc/v40/ae/infocenter/was/080701.html. |
|
Solution |
An error such as this may occur if there are incompatible
code sets between WebSphere and clients:
java.rmi.RemoteException: CORBA DATA_CONVERSION 6 No; nested exception
is:
org.omg.CORBA.DATA_CONVERSION: minor code: 6 completed: No
In JDK 1.3, the minor code 6 should have been a vendor-specific code, but
it was not. A org.omg.CORBA.DATA_CONVERSION: minor code: 6 maps to a
similar MARSHAL minor code 6 exception on Infocenter page http://www-3.ibm.com/software/webservers/appserv/doc/v40/ae/infocenter/was/080701.html:
"Character encountered while marshaling or unmarshaling a character or
string that is not ISO Latin-1 (8859.1) compliant. It is not in the range
of 0 to 255."
In JDK 1.3.1, whenever we throw a system exception, we add a reason string
as well as a minor code so this will provide a better explaination of the
problem.
For more information, the standard minor codes are defined in section
3.17.2 of the CORBA 2.3.1 spec.
In many instances, the CORBA DATA_CONVERSION minor code 6 error can be
fixed by adjusting the com.ibm.CORBA.ORBCharEncoding setting on the
application server, admin server, and/or client to allow for unicode
characters to pass.
To change the admin server setting, add the following line to the
admin.config file which resides in <WAS_Install_Dir>\bin:
com.ibm.CORBA.ORBCharEncoding=utf8
To change application server, put -Dcom.ibm.CORBA.ORBCharEncoding=utf8 in
the JVM's Command Line Arguments of the application server's which is in
the Advanced JVM Settings under the JVM Settings tab.
To change the client, include -Dcom.ibm.CORBA.ORBCharEncoding=utf8 in the
startup command line arguments of launchClient. |
|
|
|
Product
Alias/Synonym |
WAS |
|
|
|
|
|