[Incident]: Some users report they are unable to access the case portal. Please see this community notice for more information.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Additional license consumed on client reconnection

Additional license consumed on client reconnection

This is a known design limitation for Flexnet Publisher where the connecting clients checkout a new set of licenses.

Conventionally, for a client to establish connection with Server over TCP IP, a socket is created at server and client for further communication. Now, once client detects that it has been disconnected from server/the connection signature changes (bad network OR change in network), client will close the existing connection (due to security reasons) and establish a new one.

This new socket connection will lead to checkout another set of license, if DUP_GROUP is not the conventional implementation in producer's environment.

To avoid a license deadlock/shortage scenarios, the licensing administrator can always take help of options file keyword, TIMEOUT, which will automatically check-in the licenses after certain period (same as defined in options file) and help avoiding license shortage scenarios.

Additional KB on this: https://community.flexera.com/t5/FlexNet-Publisher-Knowledge-Base/Additional-license-consumed-on-client-reconnection-post/ta-p/133491

Version Fix 

The above issue has been fixed in FNP 11.18.3.0 (2021 R4) so you could run a quick test in our latest version .(FNP-18904)

 

Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Jan 12, 2022 12:35 AM
Updated by:
Contributors