Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jmeter.apache.org
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 209.85.212.178 as permitted sender)
MIME-Version: 1.0
Date: Wed, 19 Feb 2014 18:49:32 +0000
Message-ID: 
 <CAOGo0VarzRZH=1DH+TS9xsovErE8p+P8PNdfi9+nw-wXogXuzg@mail.gmail.com>
Subject: Bug 56119 - dealing with idle connection timeout and dropped
 connection
From: sebb <sebbaz@gmail.com>
To: dev@jmeter.apache.org
Content-Type: text/plain; charset=ISO-8859-1

It looks as though the problem reported in Bug 56119 was due to the
server dropping connections that have been idle too long.

There may also be servers that only allow a connection to be reused a
certain number of times (this does not seem to have been the case
here).

This email is to discuss what JMeter could perhaps do to make it
easier to test such servers.

The two existing work-rounds are:
- disable Keep-Alive
- enable staleCheck

Neither is ideal; the first is awkward to use, and staleCheck can
generate unnecessary additional traffic (which is why it was disabled
in 2.11).

I can think of two possible approaches:

1) proactively shut connections. This would be easy for servers that
limit reuse.
Just count reuses and turn off keep-alive when a specified limit is reached.
Not so easy for idle timeouts; one cannot retroactively disable keep-alive.

2) Deal with the disconnects when they occur.
The code needs to distinguish which errors are retriable, and may need
to distinguish at what point the failure occurs. For example, even a
POST ought to be retriable if JMeter is unable to send any data on the
connection.

Also need to consider how one might report retries.
I think the tester needs to be able to find out if additional requests
have been made by JMeter.