Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpClient User Discussion" <httpclient-users@hc.apache.org>
MIME-Version: 1.0
From: Benson Margulies <bimargulies@gmail.com>
Date: Mon, 20 Jun 2016 13:57:41 -0400
Message-ID: <CALhtWkdZmEfvpAmbgK3c+aNHX0_4y3TwbdH5d9p-YBE4BDvVXw@mail.gmail.com>
Subject: Telling HC to make new connections all the time
To: HttpClient User Discussion <httpclient-users@hc.apache.org>
Content-Type: text/plain; charset=UTF-8
archived-at: Mon, 20 Jun 2016 17:57:48 -0000

We use the async http components library to connect various components
in a system that is deployed, in some cases, on AWS. When it's
deployed on AWS, there are ELBs involved.

Like some other people, we've having various trauma dealing with the
very dynamic environment of AWS ELBs, which includes constant DNS
changes and some other issues. So far, we've been making our HC
configuration more and more complex. I'm wondering if we should back
off and make it simpler -- make a new connection for each request.
Obviously, this will be somewhat slower and more expensive, but at the
moment we might prefer a slower and more expensive approach that works
to one that occasionally gets lost.

I appreciate that even making new connections all the time won't
compensate for all possible DNS problems -- if Java itself caches a
stale name->address translation, making a new connection will fail
just as effectively as anything else.

Does anyone out there have advice to share (other than running away from ELB)?

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org