Contributions
Re: Since version 3.0.0 to 3.8.0 ReadyAPI starts for around 10 minutes and ends with Chromium error.
We had the same issue previously with ReadyAPI 3.6. After adding -Dsoapui.browser.disabled=true to the vmoptions file (located here: \Program Files\SmartBear\ReadyAPI-3.6.0\bin\ReadyAPI.vmoptions), the error stopped, and the client loaded faster. Now we upgraded to the latest client (v3.8.1), and this error message returns, and setting that parameter does not seem to fix it now....but maybe it will work for you!3 years agoPlace ReadyAPI QuestionsReadyAPI Questions746Views0likes0Commentscustomizable floating license timeout period
I believe the license manager for ReadyAPI has a default timeout of 12 hours of inactivity to auto check-in a floating license session. It would be really useful if that timeout period could be customizable to any time period the customer desires. Would that be possible to implement as a new feature?834Views1like2CommentsFloating license session inactivity timeout
I would like to see an option to be able to timeout floating licenses after a period of inactivity. Often all of our floating licenses are locked byusers who have logged into ReadyAPI, and then left for the day while leaving their session open. Then others are not able to aquire a floating license, so an admin has to go to the license management console and find which users should have their license session deleted. It would be greatto be able toautomatically delete sessions after aconfigurable period of inactivity.2.8KViews0likes3Comments