The ss.server_disconnect_mode option specifies what the RTserver should do, if anything, if and when an RTclient disconnects from RTserver. The three possible values are:
Setting the option to warm
is useful when an RTclient must run continuously and not lose any messages even if the RTclient crashes or the connection is accidentally terminated. In this mode, RTserver remembers the subjects being subscribed to by the disconnecting RTclient and buffers guaranteed messages. When an RTclient with the same subject name (specified using the ss.unique_subject option) reconnects to RTserver, it resends the guaranteed messages (that were saved in the buffer) to that RTclient. The RTserver option Client_Reconnect_Timeout controls the maximum amount of time, in seconds, that RTserver waits (and saves the information) for a disconnected RTclient to reconnect. If the RTclient does not reconnect to RTserver within the specified period of time, then RTserver clears the unacknowledged messages and sends a GMD_NACK message back to the sender of those 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 the disconnected RTclient process and sends a GMD_NACK message back to the sender of those messages.
Setting the option to gmd_success
is useful for short-lived operations or when an RTclient wants to exit cleanly without causing GMD failure in the sending process. In this mode, RTserver clears the guaranteed messages that have not been acknowledged by the disconnecting RTclient, but still sends an acknowledgment of delivery (a GMD_ACK message) back to the sender of those messages.
TIBCO SmartSockets™ Java Library User’s Guide and Tutorial Software Release 6.8, July 2006 Copyright © TIBCO Software Inc. All rights reserved www.tibco.com |