Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpClient User Discussion" <httpclient-users@hc.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
From: shawnh@zeptoverse.com
To: httpclient-users@hc.apache.org
Importance: Normal
Sensitivity: Normal
Message-ID: <W9053410292263801203990778@webmail4>
Date: Tue, 26 Feb 2008 01:52:58 +0000
Subject: Resetting connections
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

For a new project we're going to start using the Apache httpclient. One o=
f the things I've had trouble with in prior systems is that long-running =
services get into states where they stop operating correctly. The solutio=
n was usually to throw away the old socket and connection objects and cre=
ate new ones(discard and recreate always worked, more graceful methods di=
dn't).

What I don't see in the HttpClient / HttpConnection / HttpConnectionManag=
er is the facility to remove a specific connection from a connection pool=
 and create a new one (assuming the others are working okay). Is this han=
dled entirely within the HttpConnectionManager based on socket state and =
the type of error, or is there something additional I should do for a lon=
g-running service? (By "long-running service", I'm referring to a service=
 that should run years without intervention or restart, though "years" in=
 this case is more accurately measured in months.)

Sorry if this is a basic question, I haven't been able to find the answer=
 elsewhere or in the tutorials.

Thanks,
-- Shawn


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