jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Bazley" <>
Subject Re: ssl sessions handling
Date Mon, 18 Aug 2003 17:30:05 GMT
Unfortunately, with the default implementation, there is no control over when connections are
re-used - or not.
Furthermore, each HttpUrlConnection object can only be used once.
[I suppose the idea was to make it easy to retrieve a single item via a URL, but the design
is otherwise very inflexible,]

I may be wrong, but I don't think anything can be done until JMeter is recoded to use a more
flexible implementation, such as Apache

This should allow JMeter full control over connections, which could then be shared amongst
all samplers in a thread.

Sorry I don't have better news.
----- Original Message ----- 
From: "Laurent MEDIONI" <>
To: "'JMeter Users List '" <>
Sent: Monday, August 18, 2003 10:56 AM
Subject: RE: ssl sessions handling

I have exactly the opposite problem :)
I use JMeter 1.9..., jre 1.4.2, with SSL and Client certificate.
I cannot use one Client certificate per thread as JMeter does not provide a
way to give a separate certificate per thread (do I have to post a change
request for that ?). Thus each thread uses the same user for the
authentication process: 1st problem.
But my main problem is that each sampler in my test generates its own SSL
connection (whatever the "keep alive" option may be)... This saturates the
Apache server used to negociate SSL connections because each page, each
image, each .css, ..., opens a SSL connection: 2nd problem.

I don't know, in my case, if all SSL connections use the same SSL session
(what have you used to demonstrate that ?) but I am looking for a way to
make each thread reuse an already opened SSL connection (by the previous
sampler of the same thread).


-----Message d'origine-----
A: JMeter Users List
Date: 14.08.03 15:28
Objet: Re: ssl sessions handling

The underlying socket connections are handled by Sun's HTTPClient code,
and they are apparently reusing connections aggressively.  You will not
able to use JMeter to handle your type of authentication.

We do plan on changing to Apache's commons HTTPClient in the next
release, but I'm not sure if that will fix this problem.


On 13 Aug 2003 at 14:15, Hans Neber wrote:

> Hi
> I am using JMeter 1.8.1 and it appears that all threads get the same
> session. As our authentication mechanism is based on the ssl session I

> cannot simulate multiple sessions. It works fine when running several
> instances of JMeter with only one thread each, but this is not really
> practicable for high numbers.
> Is this behaviour known? Is anyone else having the same issue?
> Best regards, Hans
> ******************* BITTE BEACHTEN *******************
> Diese Nachricht (wie auch allfällige Anhänge dazu) beinhaltet
> möglicherweise vertrauliche oder gesetzlich geschützte Daten oder
> Informationen. Zum Empfang derselben ist (sind) ausschliesslich die
> genannte(n) Person(en) bestimmt. Falls Sie diese Nachricht
> irrtümlicherweise erreicht hat, sind Sie höflich gebeten, diese unter
> Ausschluss jeder Reproduktion zu zerstören und die absendende Person
> umgehend zu benachrichtigen. Vielen Dank für Ihre Hilfe.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Michael Stover
Yahoo IM: mstover_ya
ICQ: 152975688
AIM: mstover777

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message