Further testing has narrowed it down a little more, but is still not much
help.  It's not the 301 response code though.
The 301 redirects to:
http://www.amazon.com/exec/obidos/subst/home/home.html
which is then redirected by a 302 to
http://www.amazon.com/exec/obidos/subst/home/home.html/{someuniqueid}
It appears that enabling Retrieve All Embedded Resources from HTML Files
contributes to the problem.  If I change my test so that the path in the
request is /exec/obidos/subst/home/home.html (to skip the 301 response
entirely), enable Follow Redirects and Retrieve All..., it hangs.  If I
disable Retrieve All..., it doesn't hang.  I'm now going to dig into the
code to see if I can figure out what's going on - maybe the html parser is
choking on the response.  I did notice that the response headers are mangled
in the Sampler result tab (for the case where Retrieve All... is disabled) -
"Connection:  close" is written either as "nnCoection:  close" or
"Cneonction:  close", depending on whether I'm looking at the home.html
response or the home.html/{someuniqueid} response.  But that could be a red
herring.

Anyone with a suspicion where to look, chime in...

J
----- Original Message ----- 
From: "joelsherriff" <[EMAIL PROTECTED]>
To: "JMeter Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, July 21, 2004 1:59 PM
Subject: Head scratcher - test hanging


> Just capturing and playing back odds and ends and I have a case here that
> just hangs when playing back an http request.  Maybe someone can see
> something silly I'm doing?  I have only 1 thread group which contains only
1
> request - to www.amazon.com, path "/".  Redirect Automatically, Follow
> Redirects, and Use KeepAlive are enabled.  Thread properties is Stop Test,
> 1, 1, and 1.
> This should execute quickly, yet when I hit Start, it runs until I stop it
> but the request never completes.  The only thing of interest I can see is
> that the request gets a 301 (moved permanently) response, as opposed to
the
> more common 302.  That is, it gets it "normally", I have no way of knowing
> what's happening during the test.
>
> Any ideas?  I've attached the test plan in case anyone want's to view it.
>
> J
>
>


----------------------------------------------------------------------------
----


> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to