CORBA 2.3.3 Programmer's Reference (NonStop CORBA 2.3.7+)

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.
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
User Action: This error occurs when a Comm Server fails to its listening socket transport name.
Verify that cs_name@comm_server{tcp_process} is correctly configured.
2004 - NID interposed id Server Reply : ctx not found address
User Action: This error occurs as a Comm Server is relaying a reply message; the interposed
request id (also known as the New ID) does not map to the context held for a previously relayed
request.
2005 - Object key error. Bad system name
User Action: This error occurs when a Comm Server is relaying a request; the tsmp relay profile
contains a system name that is too large. Verify that the server@ORB{pathmon} value is
correct. If the value doesn't contain a system name, the generated one is in error. Capture the IOR
and contact your service provider.
2006 - Object key error. Bad pathmon name
User Action: This error is the same as Error 2005, except it applies to the pathmon process name.
Verify that the server@ORB{pathmon} value is correct.