cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Allow license timeouts to be seperate for floating and named licenses

Allow license timeouts to be seperate for floating and named licenses

Automatic timeouts can easily be set in order to free licenses. There is not, however, any way to distinguish between floating and named licenses. We would love to be able to set a timeout for our floating license users but not our named license users. Or, when an user clicks the Integrity logout link, the license should be freed.

6 Comments
Level 9

I cannot think of a valid use case for having a user with a named license time out.

Level 1

Correct, neither can I and that is what is frustrating. By setting the timeout to get floating licenses freed, it impacts the named licensees.

Level 7

But don't the named license users immediately re-acquire their licenses as soon as they do something in the client?  How much of an inconvenience is this?

There is one possible scenario where timing out a named license user makes sense - when the administrator has changed the membership of the named license group,  Without timing out the existing (idle) named license users, you would prevent the changes from taking effect if all licenses were in use.

Level 1


"...licenses as soon as they do something in the client?" >> The key phrase there is "do something". Users can type a whole bunch of text in a field, leave their desk for a bit, talk,  pause, etc. and then try to submit those changes. Just typing in the text, in this case, is not doing something. A connection to the server, of some sort, has to be made to be considered doing something. Users have to click a tab, link, etc. to be doing something. Correct, it is not much of an inconvenience to me, but to others it is.

Our timeout is set to 10 mins I think. I basically have to expend 3 clicks in order to re-connect and return to where I was. I probably have to do this quick series of clicks 10 times a day. It was just be nice to have named licenses always be connected (no timeouts) and have floating licenses be the ones that incur the timeout.

Level 7

If your timeout is set to 10 minutes, this is not the Idle timeout, which releases client licenses, as that has a minimum value of 60 minutes.  If it really is 10 minutes, then it is the HTTP session timeout which is kicking in.  This timeout disconnects Web clients that have been inactive for the timeout interval, and knows nothing about what license type is being used by the Web client session; it just disconnects the Web session due to inactivity.  Once the session is disconnected, it frees up the license if it is a floating license.

Level 10

You are right with the minimum of 60 minutes.

But imagine that a user is working from an offshore location with usage of a proxy in between.

If he get's disconnected (for a named license !), for next activity he needs to get reconnected first to the main server and same way to the proxy.
It won't happen in parallel.  Depending on Network Latency this will take more time than many user's patience allow. In bad cases some user kill their client with Task Manager and restart client, probably leaving open operations which can' be commited by the server but from the OS' timeout.

Under bad circumstances this have performance influence on a whole location.

I agree with that idea, but with respect to your hint a more easy reload function of all access groups (like as part of the "Refresh Realm User and Group Caches" would be very helpful in addition..