When does client's reconnect logic trigger when server terminates the connection due to heartbeat missing from client in FT setup?
Article ID: KB0093133
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
There are set of parameters that instruct the server to drop the connection when not receiving heartbeats from the client, and other set of parameters that instruct the client to drop the connection when not receiving heartbeat from the server.
- client_heartbeat_server and server_timeout_client_connection - This instructs the server when to drop the connection.
- server_heartbeat_client and client_timeout_server_connection - This instructs the client when to drop the connection.
When client comes to know the connection termination by server_heartbeat_client and client_timeout_server_connection or by OS level, reconnect logic will kick in from client side. For this ft_reconnect_timeout should be set appropriately to make sure that server won't purge the connection before reconnect kicks in.
In case, client comes to know the connection termination after ft_reconnect_timeout, reconnect attempt will fail when it tries.
For more details on these parameters, Please refer the manual.
Reconnect attempt count should be selected based on the reconnect attempt delay and ft_reconnect_timeout parameter set.
AttempCount * Attempt delay can be at the maximum of ft_reconnect_timeout value. So select the values accordingly.
There are set of parameters that instruct the server to drop the connection when not receiving heartbeats from the client, and other set of parameters that instruct the client to drop the connection when not receiving heartbeat from the server.
- client_heartbeat_server and server_timeout_client_connection - This instructs the server when to drop the connection.
- server_heartbeat_client and client_timeout_server_connection - This instructs the client when to drop the connection.
When client comes to know the connection termination by server_heartbeat_client and client_timeout_server_connection or by OS level, reconnect logic will kick in from client side. For this ft_reconnect_timeout should be set appropriately to make sure that server won't purge the connection before reconnect kicks in.
In case, client comes to know the connection termination after ft_reconnect_timeout, reconnect attempt will fail when it tries.
For more details on these parameters, Please refer the manual.
Reconnect attempt count should be selected based on the reconnect attempt delay and ft_reconnect_timeout parameter set.
AttempCount * Attempt delay can be at the maximum of ft_reconnect_timeout value. So select the values accordingly.
Issue/Introduction
When does client's reconnect logic trigger when server terminates the connection due to heartbeat missing from client in FT setup?
Feedback
Yes
No
Powered by
