Floating user - timeout?
Hi
Does anyone know what the timeout is for an RRC 2.0 floating user? I believe that as soon as one person shuts down their instance of RRC, it hands back the consumed floating license, but not sure. thanks anthony |
12 answers
the Jazz team server handles the licensing. It releases a floating license after the user has been inactive for two hours.
|
the Jazz team server handles the licensing. It releases a floating license after the user has been inactive for two hours. Thanks - good to get this clarified. anthony |
the Jazz team server handles the licensing. It releases a floating license after the user has been inactive for two hours. Thanks - good to get this clarified. anthony Actually, there is another way to interpret this question (and answers) - so let me ask it this way. If you shut down RRC (File->Exit) - so you still have to wait for two hours before another instance of RRC can pick up the license token? This is the case I want to know about. anthony |
the Jazz team server handles the licensing. It releases a floating license after the user has been inactive for two hours. Thanks - good to get this clarified. anthony Actually, there is another way to interpret this question (and answers) - so let me ask it this way. If you shut down RRC (File->Exit) - so you still have to wait for two hours before another instance of RRC can pick up the license token? This is the case I want to know about. anthony bump... |
It's my understanding, given the multiple clients connecting to the server (web and rich), and the fact that you can be logged in to multiple at the same time (and even multiple browser windows or tabs), it's hard to know when someone has really exited. So the timeout runs from last access.
My understanding may not be 100% accurate here; I hope one of the developers with intimate knowledge of this area can comment here. |
Actually from what I understand, it's a bit different than Daniel explained.
When the user interacts with the server, that license becomes consumed for the next 2 hours. Even logging off explicitly will not release it. This is how it was explained to me. Now in the case of the web ui, you may have been idle for a while prior to logging off or closing the browser, so it may not be 120 minutes from then that the license is released. However the rich client tends to be less "idle" and you may in general observe that it basically is two hours from the time you exit the client. An example of not being idle is that if you have an editor open, that artifact is checked on the server every few minutes (7 as I recall) as part of the new conflict resolution support. |
Is there a way to change the 2 hour lockout?
It seems strange, since the license should be released as soon as the user is finished with their action. If no one else can use the license for two hours then what is the point of having floating licenses? |
Geoffrey Clemm (30.1k●3●30●35)
| answered Jan 28 '10, 12:08 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
All floating licenses at Rational have a minimum timeout ... usually
ranging from 30 minutes to 2 hours. The reasons for the higher timeout value include: - fewer hits on the license server - allows the license cost to be cheaper (shorter timeout means increased shared usage, which means increased value to the customer, which means a higher price). As for what is the point of floating licenses when the timeout is two hours, imagine two scenarios: 30 occasional users, who use the system for 10 minutes once a week. With floating licenses, you probably need 2 or 3 licenses. With authorized licenses, you would need 30 licenses. Cheers, Geoff deege wrote: Is there a way to change the 2 hour lockout? |
the Jazz team server handles the licensing. It releases a floating license after the user has been inactive for two hours. Good afternoon on this subject I would like to ask how we could minimize the waiting time of two (2) hours, only to come down for a minutes? |
I don't believe it can be shortened. You could open a customer support ticket (PMR) to ask and if necessary request a product enhancement.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.