jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject RE: JMeter open sockets
Date Wed, 08 Oct 2003 14:11:16 GMT

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 []
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

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

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

-----Original Message-----
From: []
Sent: 08 October 2003 12:30
Subject: JMeter open sockets

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
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


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

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

View raw message