Hi, 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). Thanks, Laurent -----Message d'origine----- De: [EMAIL PROTECTED] 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 be 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. -Mike 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 ssl > session. As our authentication mechanism is based on the ssl session I thus > 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Michael Stover [EMAIL PROTECTED] Yahoo IM: mstover_ya ICQ: 152975688 AIM: mstover777 --------------------------------------------------------------------- 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]
