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 (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <1416649924.27014.2.camel@apache.org>
References: 
 <CAN0zEHbv_M2pssT8Kiw5=pYApF5D5eHMv=QvsoSfQMPfVv6nPw@mail.gmail.com>
	<231927678.3179369.1416603658212.JavaMail.yahoo@jws10626.mail.bf1.yahoo.com>
	<1416649924.27014.2.camel@apache.org>
Date: Sat, 22 Nov 2014 06:30:19 -0500
Message-ID: 
 <CAN0zEHazk3O_KPZ=fV3h-uaYm83i1O3z1Pa0xrKpiWy5KGqfHg@mail.gmail.com>
Subject: Re: question on idle connections
From: Sam Perman <sam@permans.com>
To: HttpClient User Discussion <httpclient-users@hc.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2d758e875af050870e2e3

--001a11c2d758e875af050870e2e3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

We're using 'EntityUtils.toString()' to consume the response on each
request. Is that not sufficient?

thanks
sam


On Saturday, November 22, 2014, Oleg Kalnichevski <olegk@apache.org> wrote:

> On Fri, 2014-11-21 at 21:00 +0000, Jaikit Savla wrote:
> > Closing Idle and Expired connection is application only when stream
> associated with Connection is closed, otherwise connections are not
> considered idle. Looks like there is leak in connections at your side.
> Below code snippet shows one example on how to close the stream in a
> guaranteed fashion.
> >         HttpResponse response =3D httpClient.execute(httpGet);
> HttpEntity entity =3D response.getEntity();        String jsonString =3D =
null;
>       try {            InputStream instream =3D entity.getContent();
> >             /* do your processing with the stream */        } finally {
>           EntityUtils.consumeQuietly(entity);        }
> > Jaikit
> >
> >      On Friday, November 21, 2014 12:48 PM, Sam Perman <sam@permans.com
> <javascript:;>> wrote:
> >
> >
>
> Jaikit is absolutely right. This section of the HttpClient tutorial may
> also be of help:
>
>
> http://hc.apache.org/httpcomponents-client-ga/tutorial/html/fundamentals.=
html#d5e145
>
> Oleg
>
> >  Hello
> >
> > We have had a persistent issue in production where after a few days our
> > PoolingClientConnectionManager becomes unusable because there are no
> > available connections. It turns out all of the available connections ar=
e
> > =E2=80=9Cleased=E2=80=9D (according to the PoolStats).
> >
> > I thought I was doing the right thing by writing an
> > IdleConnectionManagerThread as recommended in the docs. This thread wil=
l
> > call =E2=80=9CcloseExpiredConnections=E2=80=9D and =E2=80=9CcloseIdleCo=
nnections=E2=80=9D on a regular
> > interval.
> >
> > Looking at the implementation of AbstractConnPool.closeExpired and
> > AbstractConnPool.closeIdle I don=E2=80=99t understand how they work. In=
 our case,
> > all of our connections are =E2=80=9Cleased=E2=80=9D=E2=80=A6 but these =
methods only ever iterate
> > and close connections that are =E2=80=9Cavailable=E2=80=9D. How do I cl=
ean up leased
> > connections?
> >
> >             Iterator<E> it =3D this.*available*.iterator();
> >             while (it.hasNext()) {
> >                 E entry =3D it.next();
> >                 if (entry.getUpdated() <=3D deadline) {
> >                     entry.close();
> >                     RouteSpecificPool<T, C, E> pool =3D
> getPool(entry.getRoute());
> >                     pool.remove(entry);
> >                     it.remove();
> >                     notifyPending(pool);
> >                 }
> >             }
> >
> > thanks
> > sam
> > =E2=80=8B
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> <javascript:;>
> For additional commands, e-mail: httpclient-users-help@hc.apache.org
> <javascript:;>
>
>

--001a11c2d758e875af050870e2e3--