Time Session for acquired floating contributor license
7 answers
Perhaps this is what you're looking for: There is a property under
Server -> Advanced properties ->
com.ibm.team.repository.service.internal.license.FloatingLicenseService
License checkout time: 7200
The description for this property is " The amount of time (in seconds)
that a checkedot license lives before it expires" and can be set to
anything above 7200 seconds.
There is also another property under Server -> Advanced properties ->
com.ibm.team.repository.service.internal.license.LicenseService
Floating license refresh rate (in ms): 600000
Freddy
On 17/07/2010 2:08 AM, milan.krivic wrote:
Server -> Advanced properties ->
com.ibm.team.repository.service.internal.license.FloatingLicenseService
License checkout time: 7200
The description for this property is " The amount of time (in seconds)
that a checkedot license lives before it expires" and can be set to
anything above 7200 seconds.
There is also another property under Server -> Advanced properties ->
com.ibm.team.repository.service.internal.license.LicenseService
Floating license refresh rate (in ms): 600000
Freddy
On 17/07/2010 2:08 AM, milan.krivic wrote:
Hi,
Does anyone know how long is time session when user with acquired
floating contributor license is no longer active?
Is there any way to set it manually, or some period is assigned by
default?
Thanks,
The time-out for a floating license is not something you can modify.
As I recall, the time-out period is 30 minutes (but I'm not positive
about that).
There are two reasons for not having a shorter timeout:
- If the timeout is shorter, the license server would need to be hit
more often for each user, which could be a performance bottleneck.
- If the timeout is shorter, fewer licenses would be used, so the
cost/license would need to be increased (somebody has to pay all those
IBM programmers to build this cool stuff :-).
Cheers,
Geoff
On 7/16/2010 12:08 PM, milan.krivic wrote:
As I recall, the time-out period is 30 minutes (but I'm not positive
about that).
There are two reasons for not having a shorter timeout:
- If the timeout is shorter, the license server would need to be hit
more often for each user, which could be a performance bottleneck.
- If the timeout is shorter, fewer licenses would be used, so the
cost/license would need to be increased (somebody has to pay all those
IBM programmers to build this cool stuff :-).
Cheers,
Geoff
On 7/16/2010 12:08 PM, milan.krivic wrote:
Hi,
Does anyone know how long is time session when user with acquired
floating contributor license is no longer active?
Is there any way to set it manually, or some period is assigned by
default?
Thanks,
Correction based on Freddy's post ... the time-out period appears to be
2 hours. And as Freddy points out, you are allowed to increase that
timeout, to further decrease the load on the licensing server.
Cheers,
Geoff
On 7/16/2010 6:38 PM, Geoffrey Clemm wrote:
2 hours. And as Freddy points out, you are allowed to increase that
timeout, to further decrease the load on the licensing server.
Cheers,
Geoff
On 7/16/2010 6:38 PM, Geoffrey Clemm wrote:
The time-out for a floating license is not something you can modify.
As I recall, the time-out period is 30 minutes (but I'm not positive
about that).
There are two reasons for not having a shorter timeout:
- If the timeout is shorter, the license server would need to be hit
more often for each user, which could be a performance bottleneck.
- If the timeout is shorter, fewer licenses would be used, so the
cost/license would need to be increased (somebody has to pay all those
IBM programmers to build this cool stuff :-).
Cheers,
Geoff
On 7/16/2010 12:08 PM, milan.krivic wrote:
Hi,
Does anyone know how long is time session when user with acquired
floating contributor license is no longer active?
Is there any way to set it manually, or some period is assigned by
default?
Thanks,
I am viewing the list of users currently signed on to RTC, using Floating Licenses. When a user signs off, how long (if at all) is it before the license server releases the license that one user is using and makes it available to another user? If you log on and then quickly logoff (any session less than 120 minutes) does the license server automatically tie up that license for 120 minutes? If anyone has any insight into how the licenses are distributed, that information would greatly be appreciated. Thanks
Comments
Drew,
In this CLM 2012 licensing article, we added a FAQ question that states that when a user logs off the license is returned to the pool. https://jazz.net/library/article/825
I don't know if this was new behavior for v4.0 or whether it existed in v3.0.1.x.
As stated previously in this thread, the cost of a floating license is
based on the number of users that can use that license, so to decrease
the time out setting, we would need to increase the cost of a license.
Or stated in other words, to increase the number of folks that can use
the system, you need to buy more licenses.
Cheers,
Geoff
On 8/18/2010 2:22 PM, JaxJaguar wrote:
based on the number of users that can use that license, so to decrease
the time out setting, we would need to increase the cost of a license.
Or stated in other words, to increase the number of folks that can use
the system, you need to buy more licenses.
Cheers,
Geoff
On 8/18/2010 2:22 PM, JaxJaguar wrote:
So, is it or is it not possible to Decrease the time out setting for a
floating license? We need to decrease it so that more folks can use
the system. Thanks
That is correct. This ensures that at most 12 users can share a
floating license per day, and the floating license price is based on
that degree of sharing.
Cheers,
Geoff
On 8/18/2010 2:52 PM, JaxJaguar wrote:
floating license per day, and the floating license price is based on
that degree of sharing.
Cheers,
Geoff
On 8/18/2010 2:52 PM, JaxJaguar wrote:
I am viewing the list of users currently signed on to RTC, using
Floating Licenses. When a user signs off, how long (if at all) is it
before the license server releases the license that one user is using
and makes it available to another user? If you log on and then
quickly logoff (any session less than 120 minutes) does the license
server automatically tie up that license for 120 minutes? If anyone
has any insight into how the licenses are distributed, that
information would greatly be appreciated. Thanks