...
Possible callback functions are:
Name | Status | information returnedInformation Returned |
---|---|---|
HEARTBEAT_CONNECTION_LOST_FUNCTION | Connection with license server was lost. | |
HEARTBEAT_RETRY_FEATURE_FUNCTION | Reconnection with license server succeeded. Re-attempt to checkout feature from license server. | |
HEARTBEAT_CHECKOUT_FAILURE_FUNCTION | License lost; could not be regained from license server. | |
HEARTBEAT_CHECKOUT_SUCCESS_FUNCTION | License retained successfully. | |
HEARTBEAT_EXIT_FUNCTION | The automatic heartbeats thread calls this callback function when it has given up reconnecting to the license server. When using this callback, ensure you set a proper exit flag during the callback and then shut down or otherwise cease functionality of the application. |
...
- If re-checkout succeeds, the HEARTBEAT_CHECKOUT_SUCCESS_FUNCTION callback is called.
- If re-checkout fails (for example, when there are no licenses left for checkout), HEARTBEAT_CHECKOUT_FAILURE_FUNCTION is called.
- The HEARTBEAT_EXIT_FUNCTION callback is called only if the heartbeat count is exhausted.
Examples
The following examples describe callback function behavior when heartbeats are lost.
Available | serversServers | Client | actionAction | Type of | heartbeats implementedCallback function behavior when connection is lostHeartbeats Implemented | Callback Function Behavior When Connection Is Lost |
---|---|---|---|---|---|---|
S1 | CHECKOUT feature from S1 | Automatic | (LMX_OPT_AUTOMATIC_HEARTBEAT_ATTEMPTS set to 3) | |||
S1, S2, S3 | CHECKOUT feature from S1 | Automatic | (LMX_OPT_AUTOMATIC_HEARTBEAT_ATTEMPTS set to 5) | |||
S1, S2, S3 | CHECKOUT feature from S1 | Manual | (S1 goes down) | |||
S1 and S2 | CHECKOUT features A and B from S1 CHECKOUT feature C from S2 | Automatic | (LMX_OPT_AUTOMATIC_HEARTBEATS_ATTEMPTS set to 3) | |||
S1 and S2 | CHECKOUT feature from S1 | Automatic | (LMX_OPT_AUTOMATIC_HEARTBEATS_ATTEMPTS set to 3) |