We are trying to record a test on our application. We have recently
moved the application to a test server where the performance is quite
poor and the transaction that we wish to record takes upwards of 2
minutes.  What we are seeing is that ACT seems to have some sort of
retry logic when we record the test whereby if it does not get a
timely reply, it fires subsequent requests.  We seem to be measuring a
timeout of around 60s.

Has anyone seen something similar?  Is there a fix or a workaround or
is this a bug (sorry...feature ;-P)

[ Post a follow-up to this message ]

This is a known issue.  Please contact PSS for a fix if you require a
longer timeout.

Thank You

George Cheng

Microsoft Application Center & Index Server Support

Note: This article has no warranties implicit or explicit.
All the content is given on the "as is" basis and the user
takes full responsibility for its use and assumption.
Microsoft Corporation Copyright 2004
All Rights Reserved

--------------------
| From: rajeev_dutt@hotmail.com (Rajeev Dutt)
| Newsgroups: microsoft.public.applicationcenter.usage
| Subject: ACT timeout issue when recording.
| Date: 26 Aug 2004 07:14:07 -0700
| Organization: http://groups.google.com
| Lines: 10
| Message-ID: <690ff30c.0408260614.7ad6c98b@posting.google.com>
| NNTP-Posting-Host: 161.114.1.185
| Content-Type: text/plain; charset=ISO-8859-1
| Content-Transfer-Encoding: 8bit
| X-Trace: posting.google.com 1093529648 23441 127.0.0.1 (26 Aug 2004
14:14:08 GMT)
| X-Complaints-To: groups-abuse@google.com
| NNTP-Posting-Date: Thu, 26 Aug 2004 14:14:08 +0000 (UTC)
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!fr.ip.ndsoftware.net!proxad.net!postnews2.google.
com!not-for-mail
| Xref: cpmsftngxa10.phx.gbl microsoft.public.applicationcenter.usage:3879
| X-Tomcat-NG: microsoft.public.applicationcenter.usage
|
| We are trying to record a test on our application. We have recently
| moved the application to a test server where the performance is quite
| poor and the transaction that we wish to record takes upwards of 2
| minutes.  What we are seeing is that ACT seems to have some sort of
| retry logic when we record the test whereby if it does not get a
| timely reply, it fires subsequent requests.  We seem to be measuring a
| timeout of around 60s.
|
| Has anyone seen something similar?  Is there a fix or a workaround or
| is this a bug (sorry...feature ;-P)
|

[ Post a follow-up to this message ]