Server_Disconnect_Mode

The Server_Disconnect_Mode option specifies the action RTserver should take when the RT process (RTclient, RTmon, or RTgms) disconnects from RTserver. There are three possible values:

Setting the option to warm is useful when RTclient or RTmon must run continuously and not lose any messages even if it crashes or accidentally terminates. In this mode, RTserver remembers the subjects subscribed to by the disconnecting RT process and buffers GMD messages. When an RTclient or RTmon process with the same value for the Unique_Subject option reconnects to RTserver, RTserver resends the guaranteed messages to that RT process. The maximum amount of time (in seconds) RT process has to reconnect is controlled by the option Client_Reconnect_Timeout. If the RT process does not reconnect to RTserver within Client_Reconnect_Timeout seconds, RTserver clears the GMD messages that have not been acknowledged by this RT process and sends a GMD_NACK message back to the sender of these messages.

Setting the option to gmd_failure is useful for short-lived operations. In this mode, RTserver clears the guaranteed messages that have not been acknowledged by this RT process and sends a GMD_NACK message back to the sender of these messages. This is also the correct setting if your RT process is RTgms, which does not support GMD and cannot receive GMD messages.

Setting the option to gmd_success is useful for short-lived operations or when RTclient or RTmon must exit cleanly without causing GMD failure in the sending process. In this mode, RTserver clears the unacknowledged GMD messages and sends a GMD_ACK message back to the sender of these messages.

This option is required and cannot be unset.