Hi,
Regrading the mentioned scenario, there is a feature called Application timeout. In this the server can disconnect a user, and release the license for use by other users, after a pre-determined amount of time has elapsed without a Sentinel SuperPro query or heartbeat message. This helps prevent idle users from tying up licenses, and permits recovery of licenses used by aborted programs or workstations that are unexpectedly disconnected from the network.
This time is by default 120 secs. Using SuperPro APIs ( RNBOsproSetHeartBeat) or configuration file, you can define other period to override the default seconds.
For eg, RNBOsproSetHeartBeat( packet, MIN_HEARTBEAT * 3 ); gives you 60x3 = 180 secs
MIN_HEARTBEAT=60sec, so the sever will wait 180secs before releasing the license back to the pool.
Please feel free to get back in case of any query.
Thanks,
Heena
Regrading the mentioned scenario, there is a feature called Application timeout. In this the server can disconnect a user, and release the license for use by other users, after a pre-determined amount of time has elapsed without a Sentinel SuperPro query or heartbeat message. This helps prevent idle users from tying up licenses, and permits recovery of licenses used by aborted programs or workstations that are unexpectedly disconnected from the network.
This time is by default 120 secs. Using SuperPro APIs ( RNBOsproSetHeartBeat) or configuration file, you can define other period to override the default seconds.
For eg, RNBOsproSetHeartBeat( packet, MIN_HEARTBEAT * 3 ); gives you 60x3 = 180 secs
MIN_HEARTBEAT=60sec, so the sever will wait 180secs before releasing the license back to the pool.
Please feel free to get back in case of any query.
Thanks,
Heena