RTC floating license with Eclipse client
It's been found when eclipse client is used with floating license, deliver action (suspected any SCM related action would return the same behaviour) triggers license consumption for everyone who logged into the eclipse client even without any operaton performed.
Checked the following 2 references and it seems it contradicts to each other so a bit confused.
https://jazz.net/library/article/347
https://jazz.net/wiki/bin/view/Deployment/JazzLicensingExplained
Using floating developer licenses, this behaviour ends up exceeding the total number of license easily and it does not deliver the value of using floating.
Can this be considered as design fault or is there any other way to prevent any inactive user in the eclipse client to check out license?
One answer
Comments
Hi Geoffrey,
Thank you for the input. From the behaviour we observed, it seems like the case. The actual question is under usage of Floating developer license, this causes excessive licenses to be checked out so it does not work well with the intention to use the floating license. Can anybody in the development explain what would be the exact usage model of floating developer license and if this can be considered as a matter to be addressed?
Charlie, I think that's the expected behavior. As long as RTC checks for SCM information periodically (or implicitly by some operations), the license will be refreshed and the timeout starts all over again. To avoid it, try to disable the auto-refresh (although I don't know how many places you need to do this). Or manually disconnect from the connection repository. The floating concept makes perfect sense to me, particularly when you have developers working in different time slots.