COMM_FAILURE system exception. This is raised in client code when the client is waiting for a server to reply to a request but instead a communication failure occurs. If the connection is re-established the request may be retried. COMM_FAILURE system exception. The ORB raises this exception when the profiles of a remote object reference have been exhausted, meaning all profiles in the reference have been tried without success.
Suggested actions:
COMM_FAILURE system exception. This minor code indicates a failure to initialize the GIOP protocol component of a server. There are several different protocols (tcp_server, gfs_server, and tsmp_server) with different possible causes for each one.
tcp_server
tcp_process clause, and the ORB call to associate itself with that process fails, an event will be generated specifying the tcp process name (as the ORB sees it). Check that the tcp process name is correct and that the process is available. (As an example, a direct tcp server might contain the following profile: use_comm_server = not true.)
host_name or port_number clause, an event will be generated specifying which clause is missing.
<profile>@actual_tcp_address entity in the configuration database, an event will be generated specifying which step in the procedure failed.
gfs_server (GUARDIAN File System)
gfs_server has been run without a process name, an event will be generated that notes this error.
tsmp_server
tsmp_server is missing the pathmon or server_class clause, an event will be generated that specifies which clause is missing.