The HTTP Samplers use the underlying HTTP protocol implementation (standard Java or Apache HttpClient) to determine when the response data has all arrived.
Sounds like the implementation thinks all the data has arrived... Might be worth trying HTTPSampler2 (Apache HttpClient) to see if it behaves differently from HTTPSampler (standard Java). [BTW, by default, timestamps are the END of the sample, not the start. This can be changed in jmeter.properties.] S. On Wed, 17 Nov 2004 14:20:03 -0800, Brock Anderson <[EMAIL PROTECTED]> wrote: > Hi folks, > > I am using JMeter 2.0.1 to make HTTP Requests to a server that returns a > text/xml reply (GeoServer). The XML is built on-the-fly, and it is just > sent in a stream as it is made. There is often a lot of XML, and it can > take over a minute to return all the data. > > I am trying to use JMeter to track the time for the request from the > start until all the streamed XML is received. JMeter seems to stop > timing after the response headers are received. It does not wait for > all the data from the server. > > Is there an option in JMeter to wait for the full response? If not, is > there another fix for this problem? > > Thanks, > > Brock Anderson > > --------------------------------------------------------------------- > 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]
