Doors Next - Is there a License Timeout Limit?
I previously changed the FloatingLicenseService value to 7200 to extend the timeout to 2 hours, which worked as expected. Now I'm attempting to increase it to 10800. While Issued Leases displays the timeout value of 180 minutes, it continues to timeout at 120 minutes. After log in the Issued Leases timeout continues to display the remaining minutes from the 180 original value.
<o:p> </o:p>
2 answers
Comments
I did obtain advice from IBM Support for the initial change to 7200. We were hoping to change to three hours merely for the convenience of not having to log in as often. Users were finding the log in interruption disruptive in that their entry activities normally run more than two hours. Our average simultaneous use is steady at less than 50% of the available licenses, so that isn't an issue.
If you are in contact with support, I think it might be a good idea to ask them in the case too.
I have changed the value to 4 hours without any issues. Did you restart the server after setting the timeout? There are some properties that only take a new value after a restart.
Comments
Thanks for the comment, and yes, we did a restart after changing the value. We have JTS and RM on separate servers and restarted both.
Is it the license that is timing out or an idle session? With WebSphere the default idle session was 30 minutes. With Liberty Server there is no session timeout.
What attribute are you setting to increase the license timeout?