How do we extend the default deployment timeout period?

Question

Hello,

I posted this in the "Testing" forum, but got no responses in a week.  It's pretty urgent that we figure out how to extend the deployment timeout.  Here's my original post:

--

Using a Visual Studio 2008 Load Test rig, we are attempting to run a load test on an Agent that is in a different network from the Controller.  We have the Agent registered with the Controller, and we can restart the Agent from the Controller with no problems.  The external Agent is only accessible over a relatively slow network.  When we execute the load test, the deployment step pushes 17MB out to the Agent, but the load test fails with the following message:

Agent [computer] exceeded deployment timeout period.

This is not a specific test that is failing, so increasing the Test Timeout in the Test Run Config won't help.  We have modified the Controller's config file and set both AgentConnectionTimeoutInSeconds and AgentSyncTimeoutInSeconds to 12000 (and restarted the rig), but the load test continues to abort at roughly 6 minutes.

Is there a different setting that we need to change?  Perhaps the Agent config needs to be updated with a higher timeout setting?  After reviewing the config file(s) for the Agent, there does not appear to be a setting that will change the deployment timeout period for the specific Agent. 

We have been able to successfully execute the same load test on other Agents using faster network connections.  The point of this particular load test is to determine the ultimate impact of the network speeds, but we should be able to extend the timeout periods to account for the reduced speed during test preparation, right?

Any help will be greatly appreciated.  Thanks!

Answer 1

Hello,

Using a Visual Studio 2008 Load Test rig, we are attempting to run a load test on an Agent that is in a different network from the Controller.  We have the Agent registered with the Controller, and we can restart the Agent from the Controller with no problems.  The external Agent is only accessible over a relatively slow network.  When we execute the load test, the deployment step pushes 17MB out to the Agent, but the load test fails with the following message:

Agent [computer] exceeded deployment timeout period.

This is not a specific test that is failing, so increasing the Test Timeout in the Test Run Config won't help.  We have modified the Controller's config file and set both AgentConnectionTimeoutInSeconds and AgentSyncTimeoutInSeconds to 12000 (and restarted the rig), but the load test continues to abort at roughly 6 minutes.

Is there a different setting that we need to change?  Perhaps the Agent config needs to be updated with a higher timeout setting?  After reviewing the config file(s) for the Agent, there does not appear to be a setting that will change the deployment timeout period for the specific Agent. 

We have been able to successfully execute the same load test on other Agents using faster network connections.  The point of this particular load test is to determine the ultimate impact of the network speeds, but we should be able to extend the timeout periods to account for the reduced speed during test preparation, right?

Any help will be greatly appreciated.  Thanks!

Edit:  This should probably be in the Web and Load Test forum.

Answer 2

There is a quick reference guide up on Codeplex for VSTS Test Edition. It covers known issues and other helpful information about running tests. And i think this topic was covered in that guide. Maybe worth looking at.

Answer 3

From the quick reference guide on codeplex as mentioned by edaquitania it looks like you want to change the attribute with the name deploymentTimeout in the C:\Program Files\Microsoft Visual Studio 9.0\Xml\Schemas\vstst.xsd file.  Note, times are in milliseconds


<xs:element name="Timeouts" minOccurs="0">
 <xs:complexType>
  <xs:attribute name="runTimeout" type="xs:int" use="optional" default="0"/>
  <xs:attribute name="testTimeout" type="xs:int" use="optional" default="1800000"/>
  <xs:attribute name="agentNotRespondingTimeout" type="xs:int" use="optional" default="300000"/>
  <xs:attribute name="deploymentTimeout" type="xs:int" use="optional" default="300000"/>
  <xs:attribute name="scriptTimeout" type="xs:int" use="optional" default="300000"/>
 </xs:complexType>
</xs:element>

---

Tim

Answer 4

Thanks!  I'll give this a shot.  Bill Barnett also referenced this in a direct email, so I'm betting this will solve the problem.  It's interesting that these settings are not exposed in the Test Run Config editor in VS.

Answer 5

Hi, I was wondering if changing the deploymentTimeout value addressed your problem.

I have pretty much the same problem that was described in the original post.  The controller and agent are on the same network, but other than that it's the same.

I changed the deploymentTimeout value and restarted the rig, but I still get "Agent <agent name> exceeded deployment timeout period" after about 5 minutes.

One interesting thing I find is that even though I get the timeout message and the test stops, the deployment continues.  It takes about 15 minutes, but all the assemblies eventually deploy to the Deployment folder.

I turned on logging on the agent and see this.  Why is the agent looking for the deployment job after 5 minutes?  Any assistance would be GREATLY appreciated.

[I, 2808, 3, 2009/09/12 22:04:23.549] QTAgentService.exe: Copying remote file: C:\Documents and Settings\dwhalen\Local Settings\Application Data\VSEQT\QTController\3e94bd50-af99-462d-9947-369d45f09491\Deployment\wcfload.dll to: C:\Documents and Settings\dwhalen\Local Settings\Application Data\VSEQT\QTAgent\3e94bd50-af99-462d-9947-369d45f09491\Deployment\wcfload.dll
[V, 2808, 5, 2009/09/12 22:04:35.721] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:05:05.361] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:05:35.407] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:06:05.313] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:06:35.374] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:07:05.405] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:07:35.389] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:08:05.404] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:08:35.388] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:09:05.356] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 6, 2009/09/12 22:09:22.606] QTAgentService.exe: DeploymentQueue: Deployment job was not found for run 3e94bd50-af99-462d-9947-369d45f09491
[V, 2808, 6, 2009/09/12 22:09:23.762] QTAgentService.exe: AgentService: calling AgentObject.AbortTests
[V, 2808, 6, 2009/09/12 22:09:24.012] QTAgentService.exe: AgentService: calling AgentObject.Cleanup
[V, 2808, 5, 2009/09/12 22:09:35.387] QTAgentService.exe: AgentService: Connection to controller is up.
[E, 2808, 10, 2009/09/12 22:10:01.761] QTAgentService.exe: AgentService: Exception while calling AgentEvent on controller: Microsoft.VisualStudio.TestTools.Exceptions.EqtException: Couldn't find connection object

Server stack trace:
   at Microsoft.VisualStudio.TestTools.Common.ConnectionManager`1.UpdateAccessTime(ConnectionType connection)
   at Microsoft.VisualStudio.TestTools.Controller.AgentManager.UpdateAgentAccessTime(AgentMachine agent)
   at Microsoft.VisualStudio.TestTools.Controller.ControllerObject.AgentEvent(String agentName, TestMessage message)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.VisualStudio.TestTools.Controller.IControllerCallback.AgentEvent(String agentName, TestMessage message)
   at Microsoft.VisualStudio.TestTools.Agent.AgentService.Microsoft.VisualStudio.TestTools.Controller.IControllerCallback.AgentEvent(String agentName, TestMessage message)
[V, 2808, 6, 2009/09/12 22:10:05.370] QTAgentService.exe: AgentService: calling AgentObject.Hello
[I, 2808, 5, 2009/09/12 22:10:05.652] QTAgentService.exe: AgentService: Connection to controller is down. Reconnecting...
[I, 2808, 5, 2009/09/12 22:10:05.652] QTAgentService.exe: AgentService: connecting to controller using uri: tcp://col-dwhalen-lt:6901/ControllerAccessManager.rem
[I, 2808, 5, 2009/09/12 22:10:05.995] QTAgentService.exe: AgentService: obj is Microsoft.VisualStudio.TestTools.Controller.ControllerObject
[V, 2808, 6, 2009/09/12 22:10:06.245] QTAgentService.exe: AgentService: calling AgentObject.Hello
[V, 2808, 5, 2009/09/12 22:10:06.480] QTAgentService.exe: AgentService: Successfully connected to controller.
[V, 2808, 5, 2009/09/12 22:10:35.401] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:11:05.401] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:11:35.259] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:12:05.384] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:12:37.149] QTAgentService.exe: AgentService: Connection to controller is up.
[I, 2808, 3, 2009/09/12 22:12:37.243] QTAgentService.exe: Copying remote file: C:\Documents and Settings\dwhalen\Local Settings\Application Data\VSEQT\QTController\3e94bd50-af99-462d-9947-369d45f09491\Deployment\WCFLoad.pdb to: C:\Documents and Settings\dwhalen\Local Settings\Application Data\VSEQT\QTAgent\3e94bd50-af99-462d-9947-369d45f09491\Deployment\WCFLoad.pdb
[V, 2808, 5, 2009/09/12 22:13:05.398] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:13:35.320] QTAgentService.exe: AgentService: Connection to controller is up.
[V, 2808, 5, 2009/09/12 22:14:05.397] QTAgentService.exe: AgentService: Connection to controller is up.
Continues deploying all the other files....

Answer 6

I have the same issue with VS2010 test controller and agent. All files are copied as expected but the test run fails with "Agent exceeded deployment timeout period."

Changing the settings as instructed above did not help for me as well.

 

DWWhalen,

 

Have you resolved the issue yet? Please let me.

 

Thanks,