Here is the response we received from the HPE Research and Development team:![alt text][1]

From the logs generated it was shown that the webgate was timing out after 120s from the initial request, once the timeout was reached, the webgate would try again to send the request against the server. So what we are seeing here is the constant request sent from the webgate to the server, but that request is not being answered on those 120s so the request is sent again.

So to correct that behavior we can increase that timeout, and take it from there.

To increase it you need to follow these steps:

1. Open the following url: http://:/qcbin/Apps
2. Click on the ''Webgate Customization Tool''. This is an executable, so you can download it or execute it directly
3. Locate the ''General HTTP Settings''
4. Increase the value under the ''Connection Timeout'' to 18000 and then replicate the issue.

Now, I found another way to change the webgate timeout that could probably help you to spread the fix among the users. The webgate timeout stores its value on a Windows Registry key found under: HKEY_CURRENT_USERSoftwareMercury InteractiveTestDirectorWEB

There you would find a key named ''CONNECTION_TIMEOUT'', this is the key that controls the webgate timeout so you can increase the value to the suggested one. To modify the value you just need to do right click and select ''Modify''.

Usually when this type of request happens, the IT team would do the change using a script file that is being pushed to the computers using an IT policy.

![alt text][2]

[1]: /storage/temp/515-webgate-customization.png
[2]: /storage/temp/516-registry-connection-timeout.png