You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Felix van Hove <fe...@de.easynet.net> on 2004/06/17 21:06:43 UTC
testing HTTPS
According to bug 29378 JMeter doesn't reuse HTTPS connections, when keep-alive
is enabled. I can confirm this for 2.0.1 and the HTTP Request Sampler. This
behaviour is especially annoying, because the once used connections stay
established for some time.
We do need to test HTTPS, so I tried the new HTTP Request HTTPClient (Alpha). It
doesn't show this behaviour. I'm using the number of used local ports as a
measure, something like netstat|grep https|wc -l to watch it. It's promising,
the number of connections permanently corresponds the number of threads. Some
results I got, using a thread group, 10 threads, iterating one minute:
HTTP Request: between 9 and 10 connections, 1260 requests.
HTTP Request with keep-alive: growing to 389 connections, 1027 requests.
HTTP Request HTTPClient (Alpha): between 9 and 10 connections, 1225 requests.
HTTP Request HTTPClient (Alpha) with keep-alive: 10 connections, 1267 requests.
What restrictions do I have to expect, when using the HTTP Request
HTTPClient-Alpha? Did anybody recognize bugs? Or is it allready used a lot?
Thanks.
Felix van Hove
--
easynet GmbH (http://www.de.easynet.net)
Felix van Hove, system integration
Harburger Schlossstrasse 1, D-21079 Hamburg
fon: +49-40-77175-457, fax: +49-40-77175-498
# easynet is part of the easynet group plc (www.easynetgroup.net)
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: testing HTTPS
Posted by Michael Stover <ms...@apache.org>.
Furthermore, if you're a developer, maybe consider improving it for your
needs and contributing your improvements back to Apache.
:-)
-Mike
> The HTTPClient code is Apache code - see
> http://jakarta.apache.org/commons/httpclient/ for details - and is used by
> quite a few projects. [JMeter is using version 2.0 at present.]
>
> However the JMeter sampler that uses it is new, and some features have not
> yet been implemented (e.g. Post probably does not work) which is why it is
> shown as Alpha code.
>
> If you do discover any problems or missing functionality, please let us
> know.
> Equally, if you have been using it successfully under heavy loads, it would
> also be useful to know.
>
> Sebastian
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
--
Michael Stover <ms...@apache.org>
Apache Software Foundation
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: testing HTTPS
Posted by Sebastian Bazley <se...@apache.org>.
----- Original Message -----
From: "Felix van Hove" <fe...@de.easynet.net>
To: <jm...@jakarta.apache.org>
Sent: Thursday, June 17, 2004 8:06 PM
Subject: testing HTTPS
> According to bug 29378 JMeter doesn't reuse HTTPS connections, when
keep-alive
> is enabled. I can confirm this for 2.0.1 and the HTTP Request Sampler.
This
> behaviour is especially annoying, because the once used connections stay
> established for some time.
The java.net package HTTP functionality is quite basic, which is why we have
started using HTTPClient as well.
> We do need to test HTTPS, so I tried the new HTTP Request HTTPClient
(Alpha). It
> doesn't show this behaviour. I'm using the number of used local ports as a
> measure, something like netstat|grep https|wc -l to watch it. It's
promising,
> the number of connections permanently corresponds the number of threads.
Some
> results I got, using a thread group, 10 threads, iterating one minute:
>
> HTTP Request: between 9 and 10 connections, 1260 requests.
> HTTP Request with keep-alive: growing to 389 connections, 1027 requests.
> HTTP Request HTTPClient (Alpha): between 9 and 10 connections, 1225
requests.
> HTTP Request HTTPClient (Alpha) with keep-alive: 10 connections, 1267
requests.
That's encouraging.
>
> What restrictions do I have to expect, when using the HTTP Request
> HTTPClient-Alpha? Did anybody recognize bugs? Or is it allready used a
lot?
>
The HTTPClient code is Apache code - see
http://jakarta.apache.org/commons/httpclient/ for details - and is used by
quite a few projects. [JMeter is using version 2.0 at present.]
However the JMeter sampler that uses it is new, and some features have not
yet been implemented (e.g. Post probably does not work) which is why it is
shown as Alpha code.
If you do discover any problems or missing functionality, please let us
know.
Equally, if you have been using it successfully under heavy loads, it would
also be useful to know.
Sebastian
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org