You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by "Smits.Dolf" <do...@siemens.com> on 2005/07/06 19:48:44 UTC

Problem with connections

Hi all,
 
Im running Jmeter on a local machine, generating a severe load on the
server.
The tests fail because the server is getting to much connections.
 
I use a thread group, existing of 95 threads.
The thread group contains a loop controller which loops 100 times. In the
loop, a connection is setup, some requests are performed, and the connection
is closed.
 
To my understanding, in the loop, the next request is sent as the previous
request is received, so I should end up with maximum 95 connections.
 
OR, wil the loop send out all requests as fast as possible, without waiting
for responses? In that case I could indeed end up with 95*100 =9.500
connections to the server.
 
If my understanding is correct, the problem is in the closing of the
connections.
 
Has anyone experience with JMeter not closing the connections properly, or
the server not closing the connections properly and can he/she give me some
hints how to handle this problem.
 
I/m using the LDAP protocol, so this is not stateless but is depending on a
session.
I'm running both the server and the client on a 8cpu SUN solaris 10 server
with 48 Gb memory.
 
Any hints are welcome.
 
Dolf

Dolf Smits 
Senior Consultant Meta Directory Solutions 

Siemens Nederland N.V. 
COM EN

Bezoekadres 
Prinses Beatrixlaan 800 
Den Haag 

Correspondentieadres 
Postbus 16068 
NL-2500 BB  Den Haag 

070 333 3654 
070 333 2511 
06 55844837 
Dolf.Smits@siemens.com 
www.siemens.nl 



Deze e-mail is uitsluitend bedoeld voor kennisneming door de
geadresseerde(n), en mag niet aan anderen worden doorgestuurd of op andere
wijze ter kennis worden gebracht. Indien u niet de geadresseerde bent,
verzoek ik u om de afzender te waarschuwen en de e-mail direct te
verwijderen/vernietigen. De afzender wijst elke aansprakelijkheid voor (de
inhoud van) deze e-mail af.

 

Re: Problem with connections

Posted by sebb <se...@gmail.com>.
On 7/6/05, Smits.Dolf <do...@siemens.com> wrote:
> Hi all,
> 
> Im running Jmeter on a local machine, generating a severe load on the
> server.
> The tests fail because the server is getting to much connections.
> 
> I use a thread group, existing of 95 threads.
> The thread group contains a loop controller which loops 100 times. In the
> loop, a connection is setup, some requests are performed, and the connection
> is closed.
> 
> To my understanding, in the loop, the next request is sent as the previous
> request is received, so I should end up with maximum 95 connections.

The existing samplers work on the request-response principle, and a
thread will not continue until the sampler has read the response (or
it timed or or failed etc).

> OR, wil the loop send out all requests as fast as possible, without waiting
> for responses? In that case I could indeed end up with 95*100 =9.500
> connections to the server.

No.

> If my understanding is correct, the problem is in the closing of the
> connections.

Perhaps.
 
> Has anyone experience with JMeter not closing the connections properly, or
> the server not closing the connections properly and can he/she give me some
> hints how to handle this problem.
> 
> I/m using the LDAP protocol, so this is not stateless but is depending on a
> session.

Not sure how the LDAP Sampler handles connection closure/re-use.

BTW, which one are you using?

> I'm running both the server and the client on a 8cpu SUN solaris 10 server
> with 48 Gb memory.
> 
> Any hints are welcome.
> 
> Dolf
> 
> Dolf Smits
> Senior Consultant Meta Directory Solutions
> 
> Siemens Nederland N.V.
> COM EN
> 
> Bezoekadres
> Prinses Beatrixlaan 800
> Den Haag
> 
> Correspondentieadres
> Postbus 16068
> NL-2500 BB  Den Haag
> 
> 070 333 3654
> 070 333 2511
> 06 55844837
> Dolf.Smits@siemens.com
> www.siemens.nl
> 
> 
> 
> Deze e-mail is uitsluitend bedoeld voor kennisneming door de
> geadresseerde(n), en mag niet aan anderen worden doorgestuurd of op andere
> wijze ter kennis worden gebracht. Indien u niet de geadresseerde bent,
> verzoek ik u om de afzender te waarschuwen en de e-mail direct te
> verwijderen/vernietigen. De afzender wijst elke aansprakelijkheid voor (de
> inhoud van) deze e-mail af.
> 
> 
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org