CORBA 2.6 Programmer's Reference
configured profile that has a port number of zero. Change the configured profile so that the port
number is nonzero.
1635 - (ZDOM-ORB-ERR35)
User Action: The Java ORB contains an internal event framework used to access the standard
TCP/IP, File System and Pathway protocols. If there is a critical error during the processing of a
framework event message, the Java ORB will generate a ZDOM-ORB-ERR35 message with the
current Java stack trace as the message body. The event framework then exits the application. This
message reflects a critical error during event framework processing. The Java stack trace provides
detailed information of the calling sequences executed prior to exiting the application.
1636 - (ZDOM-ORB-ERR36)
User Action: This error occurs when there is a Portable Interceptor error. The detailed error
message explains the problem.
1637 - (ZDOM-ORB-ERR37)
User Action: This error occurs when there is an initialization error. The detailed error message
explains the problem.
1640 - (ZDOM-ORB-ERR40)
User Action: This error indicates that an attempt has been made to send wchar or wstring data in a
GIOP 1.0 message (wstring/wchar data is unsupported in GIOP 1.0). Either modify the GIOP
version in the entity associated with the client or server to GIOP 1.1 or 1.2 using the giop_version
configuration key, or set the entity's allow_wchar_wstring_in_1.0 key value to true.
1641- (ZDOM-ORB-ERR41)
User Action: This error indicates the application has been configured with an invalid
wchar_native_code_set@ORB value. The value should be either UCS-2 or UTF-16.
Comm Server Error Messages (Error numbers 2000
- 2199)
2001 - Configuration error. CommServer name has no host name
User Action: This error occurs when a comm server fails to find the
cs_name@comm_server{host_name} key in the configuration database. Verify that the
Comm Server server pool has the correct NSDOM_CFG_DBM env. Also verify that the Comm
Server server pool and the configuration database names are correct.
2002 - Configuration error. CommServer name has no port number
User Action: This error occurs when a Comm Server fails to find the
cs_name@comm_server{port_number} key in the configuration database. Verify that the
Comm Server server pool has the correct NSDOM_CFG_DBM env. Also verify that the Comm
Server server pool and the configuration database names are correct.
2003 - Configuration error. Failed to set tcp_process