Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: JMeter open sockets
Date: Wed, 8 Oct 2003 15:11:16 +0100
Message-ID: 
 <934C8C7648FCD14CB2DAB9E45065708D026FB341@i2km08-ukbr.domain1.systemhost.net>
Thread-Topic: JMeter open sockets
Thread-Index: AcONlBiN7UxWUkp3TaSLabuWXPJRugAEcX4w
From: <jose.3.kuzhivelil@bt.com>
To: <jmeter-user@jakarta.apache.org>


Thanks for that info, but it didnt work for us, i'm trying to track down =
the setKeepAlive method calls in the src now.
but the netstat still shows the same number of open sockets all the way =
until the test ends.

- Jose


-----Original Message-----
From: BAZLEY, Sebastian [mailto:Sebastian.BAZLEY@london.sema.slb.com]
Sent: 08 October 2003 13:02
To: 'JMeter Users List'
Subject: RE: JMeter open sockets


Yes it is, unfortunately.

The default HttpUrlConnection implementation provides no control over =
when
sockets are re-used, and does not allow more than one request per
connection. [Nor does it allow one to specify HTTP version, as far as I =
can
tell.]

You should find you get better behaviour by setting keep-alive to false, =
as
this should cause JMeter to tell the server to close the connection =
right
away.

You probably will get lower throughput on the server, but at least you
should be able to establish a lower-bound for the server performance.

Let us know if this helps.

There are plans to move to a different HTTP protocol package sometime in =
the
future...

S.
-----Original Message-----
From: jose.3.kuzhivelil@bt.com [mailto:jose.3.kuzhivelil@bt.com]
Sent: 08 October 2003 12:30
To: jmeter-user@jakarta.apache.org
Subject: JMeter open sockets


Hi,
=20
I'm running a test of 50 threads through a Thread Group of 90 requests, =
I
was expecting 50 sockets opened on the server but I found that there =
were
actually one socket opened per request per thread (totalling 4500 open
sockets) and my server eventually ran out of memory and  I had to shut =
down
the test and the server.
Eventually it took around 4 minutes to release these connections as well =
but
that is the default keep-open value in unix I guess
=20
My question is whether this is the expected behaviour in JMeter that it
opens a new Connection per HTTP request or have i not set something
correctly?=20
=20
Regards
Jose

=20

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


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