Even though the server to server heart beat is not configured in the configuration files, still heart beat flows between servers? Is that expected?
Article ID: KB0089931
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Yes, it is expected. In the recent version of EMS server, we introduced configuration parameters to control the heartbeat interval and Timeout Value in the way we want to control. But there were under lying heartbeat flows even if we don’t configure it to keep the connection alive. It sends in a regular interval of time. Especially this is useful when firewall exists between the servers. If there is no activity on the connection for some time, firewall might close that port and connection between the servers will be gone.
By configuring the heartbeat interval and timeout between servers, we can expedite the closing of the connection between servers in the logical level Instead of underlying default OS mechanism to handle.
Yes, it is expected. In the recent version of EMS server, we introduced configuration parameters to control the heartbeat interval and Timeout Value in the way we want to control. But there were under lying heartbeat flows even if we don’t configure it to keep the connection alive. It sends in a regular interval of time. Especially this is useful when firewall exists between the servers. If there is no activity on the connection for some time, firewall might close that port and connection between the servers will be gone.
By configuring the heartbeat interval and timeout between servers, we can expedite the closing of the connection between servers in the logical level Instead of underlying default OS mechanism to handle.
Issue/Introduction
Even though the server to server heart beat is not configured in the configuration files, still heart beat flows between servers? Is that expected?
Feedback
Yes
No
Powered by
