Working of MAX_CONNECTIONS Functionality in Detail
- With MAX_CONNECTIONS value set(A), license administrator can set the limit on number of connections(of any type) which can be established with vendor daemon.
- In case, MAX_CONNECTIONS value set(B), is greater than soft limit(A) on the machine then soft limit value supersedes the MAX_CONNECTIONS value(B). Following code snippet provides the value to vendor daemon on the soft limit : -
getrlimit(RLIMIT_NOFILE, &openFdLimit); fdLimit = (int) openFdLimit.rlim_cur;
- Vendor daemon reserves(RU) 30 connections for important FNP utilities(lmreread, lmstat etc.) so to avoid outage while using them. It means if value of A is 100 then number of client connections which can be established with vendor daemon is B(70) = A(100) - 30(RU).
- In case point 2) is valid then another 30 connections vendor daemon reserves(RV) for itself. In that case, B(40) = A(100) -30(RU) - 30(RV)
- Value of A cannot be less than 31.
- Utilities can also use buffer (B) until it is not exhausted. Buffer(RU) will only be used once (B) is exhausted.
- Vendor daemon functionality keeps increment the counter on every socket connection.
- Once number of connections exceeding 80% of the threshold limit(B), vendor daemon starts displaying warning messages on every successive socket connection.
- Once number of connection established with vendor daemon reached to threshold limit(B), further all connection request will be dropped(exception utilities), until some the established connections are dropped.