Summary
This article discusses the HEARTBEAT_INTERVAL property to allow users to avoid timeouts due to network latency over large distances
Synopsis
What are the network latency constraints for running a three server configuration for FlexNet Publisher license servers?
I have read the Selecting a License Server Machine and the Network Bandwidth for License Server sections of the FlexNet Publisher License Administration Guide but am looking for more concrete information and numbers if possible.
Discussion
The HEARTBEAT_INTERVAL value is the correct method of increasing the available time to compensate for any latency between the servers.
When a license server comes up in a three server redundancy setup, it immediately tries to communicate with the other servers and will be unable to serve licenses until it has made at least one connection (referred to as a quorum). Setting the HEARTBEAT_INTERVAL on the server line of a license configures how long the server will wait to receive a response from a heartbeat.
The following information relating to the HEARTBEAT_INTERVAL is taken from the Using Other Capabilities with Three-Server Redundancy section of the FlexNet Publisher Programming Reference for License File Based Licensing:
HEARTBEAT_INTERVAL=seconds
This indicates how long the license servers wait to receive a heartbeat from another license server before shutting down the vendor daemon. This value is used in the following equation to calculate the actual timeout value:
timeout = (3 * seconds) + (seconds * 1)
Valid timeout value is 0-120. The default value is 20, which equates to an actual timeout of 79 seconds. Valid seconds values are 0 through 30. This parameter is optional and should be placed on the first SERVER line in the license file. This value can be changed after the license file has been signed. The license server must be running a version 10.8 or later vendor daemon to use this keyword.
The information above shows that while the default value is 20, this can be configured to be as high as 120 should this be required.
Related Articles
How To Specify Multiple IP Addresses in FlexNet Publisher License File 9Number of Views Building an Installer for FlexNet Publisher License Server 6Number of Views What is the Difference Between Standard and Current Properties / Filters / Segments? 15Number of Views FlexNet Publisher versus FlexNet Embedded license server 18Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago