Configuration’s Lock Timeout feature

  • Questions
  • Configuration's Lock Timeout feature
Question ID: 108348
0
0

So unless I’m not understanding the "LOCK_TIMEOUT" feature, this is not working. I know the default is 10 hours, but I moved from 10 to 2 hours month ago. We are hitting our full license limit (27) at least 3 times in a week. I wanted to move from 10 hours to 2 for any inactivity on QC so it will kick the person out of the system.

I know the documentation shows the following comment for this setting.
LOCK_TIMEOUT

Description: The maximum number of hours that ALM objects can remain locked. After this time, the lock is removed. By default, the value is set to 10 hours.

Marked as spam
Posted by (Questions: 113, Answers: 8)
Asked on April 30, 2018 3:25 pm
45 views
Answers (1)
0
Private answer

The problem is not the LOCK_TIMEOUT parameter it is the WAIT_BEFORE_DISCONNECT parameter.

Only the client uses the WAIT_BEFORE_DISCONNECT parameter. While the client is running every 5 minutes it will send a ping to the server letting the server know it is still active. I will send these pings for the amount of time specifed in the WAIT_BEFORE_DISCONNECT parameter which in your case would be 480 minutes or 8 hours. Once there have been 8 hours of inactivity then since you have the AUTO_LOGOUT_ON_SERVERR_DISCONNECT set to Y then the user will get a message saying that they have been logged out.

On the server there is a process that runs every 15 minutes to look for sessions that have not pinged the server in the last 10 minutes. Sessions that have not pinged the server in the last 10 minutes are cleared and the license is released

So with your configuration it could take up to 8 hours and 25 minutes for the licenses to be returned to the license pool.

The LOCK_TIMEOUT sets how long an object can stay locked in the database. Meaning if someone was working on creating a test that object would be locked. If the browser crashed that lock might no get removed and the object would stay locked till the LOCK_TIMEOUT is reached.

You would need to change the WAIT_BEFORE_DISCONNECT parameter if you are having an issue with licenses being released.

Marked as spam
Posted by (Questions: 0, Answers: 310)
Answered on April 30, 2018 3:26 pm