>There is no such feature in JMeter.
Couldnt you do this at a HTTPClient level by setting it in
httpclient.properties? or does Jmeter always override?


On Thu, Oct 17, 2013 at 4:03 AM, sebb <[email protected]> wrote:

> On 14 October 2013 18:35, Rittenhouse, Dan <[email protected]>
> wrote:
> > Can someone point me to any secondary documentation on setting default
> timeouts for the entire transaction not just the connections.
>
> There is no such feature in JMeter.
> The most you can do is use an Assertion to check the elapsed time.
>
> > I check the manual but when I do as they suggest which is to set a
> "Timeout" parameter in HTTP Requests Defaults, it doesn't work as I would
> expect.  If I set for under a second like 500ms, it time-out right away
> doesn't even wait a half a second.  If I set it to over a second, 1000ms,
> it waits for well over a second before timing out.
>
> Try setting the timeouts on the HTTP Request itself.
> If that does not work, then it sounds like a bug in the JVM.
> Or possibly the server is sending small chunked responses with large
> gap between them.
> The response timeout applies to each individual read from the socket,
> not the overall response time.
> To check that, you need an Assertion.
>
> > Any help would be appreciated,
> >
> > Dan
> > ---------------------------------------------------------------------
> > 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