Hi Sebastian, Thanks for the response.
I am using JMeter 2.0 with the default HTTP sampler and Tomcat 4.1. After a little bit of playing with tcpdump I can confirm that, if keep-alive is being used, *each thread* gets its own connection and will handle 100 requests using that connection before re-establishing it. I am not sure whether it is Tomcat or JMeter that breaks the connection after each 100 requests (Tomcat does *not* have maxKeepAliveRequests specified for the Coyote connector). Regards, Ryan. -----Original Message----- From: BAZLEY, Sebastian [mailto:[EMAIL PROTECTED] Sent: 22 April 2004 12:27 To: 'JMeter Users List' Subject: RE: Number of HTTP connections if using keep-alive Depends on the version of JMeter and the Http implementation. If using 2.0, and the new HttpSampler (which uses Apache HttpClient), then it should be 1 per thread, though this has not been confirmed. If this is not the case, please file a Buzilla report, as the intention was to re-use connections if so requested. If using the default Http implementation, who knows? The standard Java interface offers no way to re-use connections. If keep-alive is set, it is up to the Java implementation as to what it does. Sebastian -----Original Message----- From: Ryan Lissack [mailto:[EMAIL PROTECTED] Sent: 22 April 2004 11:31 To: '[EMAIL PROTECTED]' Subject: Number of HTTP connections if using keep-alive Hi, How many HTTP connections will JMeter 2.0 make if the server is using keep-alive? 1 per thread / 1 per thread group / 1 per test ? Thanks, Ryan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___________________________________________________________________________ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. ___________________________________________________________________________ --------------------------------------------------------------------- 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]
