Resolution:
A network failure was detected on a connection. The connection should be destroyed; and, a new connection created, if necessary.

There are two reasons a client would throw a 514.

1). The client has no communication with the server for X period of time.
By default, in the client,  the option server_read_timeout is set to 30 seconds and the option server_keep_alive_timeout is 15 seconds, so the client would have to go through a period of 30 seconds where it had no communication with the server and then would send a keep_alive to the server. If the connection to the server is gone or the server does not respond to the keep_alive request within server_keep_alive_timeout amount of time the client will initiate a destroy on its side of the connection and report the 514 error.

2). The client tried to write on a connection to the server (either sending a message or a keep_alive) and the write failed within Server_Write_Timeout amount of seconds (default 30).

In both instances the error 514 indicates that the reporting process will execute its fatal error callback (disconnect warm and then reconnect full in the case of an RTclient).

Note: An Error Code of 10 (T_ERR_END_OF_FILE), discovered during a read attempt, means that the process at the other end closed the connection and an error Code of 514 means that the reporting process did. If using the Java API the client will see the following : "reader: in: connection dropped" which is equivalent to an Error Code of 10 (T_ERR_END_OF_FILE)

What does IPC Error Code 514 T_ERR_FAILURE_DETECTED mean?