Progress® Telerik® Test Studio® Feedback Portal
Back to Feed
Request a Feature Report a Bug
Completed
Last Updated: 15 May 2014 10:00 by ADMIN
ADMIN
Cody
Created on: 04 Apr 2014 14:25
Type: Bug Report
1
Execution Server getting SQL Server timeouts (from storage service) from DB that has grown to 1.2GB.
A customers project is filling the DB really fast. After two days of operation it grows to 1.2 GB in size. When it gets this large remote execution stops working. We spent quite a bit of time troubleshooting the root cause. What we discovered is that a specific request from the Execution Server to Storage Service is resulting in a SQL DB timeout. Storage Service has a hard coded timeout of 30 seconds for SQL queries. Storage Service is reporting it has hit this timeout for the specific request it received.
2 comments
ADMIN
Daniel Djambov
Posted on: 15 May 2014 10:00 
Telerik: the implemented fix will be available in our next product release planned by the end of May 2014.
ADMIN
Daniel Djambov
Posted on: 15 May 2014 07:41 
Telerik: we have implemented an option to increase the timeout of the Storage Service calls to SQL DB which will help in most such scenarios. There is a new setting in the config file of the storage service located by default here C:\Program Files (x86)\Telerik\Test Studio\StorageService\CloudStorageSelfHost.exe.config, which can be found in <appSettings> and now defaults to 180 seconds instead of 30. If changed and then service is restarted new change will take effect:
 <appSettings>
    <add key="CommandTimeOut" value="180"/>
  </appSettings>
Create an account Log In
View
Type
Status