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: pass (nike.apache.org: domain of lainhart@us.ibm.com designates
 32.97.182.139 as permitted sender)
In-Reply-To: <541889B0.8020708@apache.org>
References: 
 <OF403D2078.6A1E02B9-ON85257D54.004EE607-85257D54.00533279@us.ibm.com>
 <1410856202.17023.14.camel@ubuntu>
 <OF8BB87694.1146E9A7-ON85257D55.004EB2EF-85257D55.004F19E1@us.ibm.com>
 <541889B0.8020708@apache.org>
To: "HttpClient User Discussion" <httpclient-users@hc.apache.org>
MIME-Version: 1.0
Subject: Re: PoolingHttpClientConnectionManager and CloseableHttpResponse
Message-ID: 
 <OF3B9870EC.C87B93F8-ON85257D55.006AE625-85257D55.006CEC6B@us.ibm.com>
From: Todd W Lainhart <lainhart@us.ibm.com>
Date: Tue, 16 Sep 2014 15:49:44 -0400
Content-Type: multipart/alternative;
 boundary="=_alternative 006CEC6B85257D55_="

--=_alternative 006CEC6B85257D55_=
Content-Type: text/plain; charset="US-ASCII"

> 
> The connection manager has no way of knowing if a connection is still 
> being used. No matter what it needs to be notified that the connection 
> can be re-claimed (and either kept alive for further re-use or 
> discarded). The #release method looks like a natural way of doing that.
> 
> Oleg
> 

Thanks - I'm still trying to grok, at a lower-level, the relationship 
between the connection, the manager, and the pool.  I've got past the 
connection pool shutdown problem (my code).  I'm now seeing ISE raised on 
an unexpectedly closed HttpConnection (stack trace below).  I'm not 
getting this one, as the RequestExecutor is successfully sending the 
request, but it's erring out on the closed connection.

Assuming that the connection is not shared across threads, and not being 
closed by another thread, what would be a cause of the unexpected 
connection close between the request and response?

Thanks for your help.  My suspicion is that there is still someone holding 
onto a connection, while in parallel, the connection manager from which 
that connection was provisioned is shutdown. I'm wondering if there might 
be another scenario.


Caused by: java.lang.IllegalStateException: Connection is not open
        at org.apache.http.util.Asserts.check(Asserts.java:34)
        at 
org.apache.http.impl.BHttpConnectionBase.ensureOpen(BHttpConnectionBase.java:128)
        at 
org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseEntity(DefaultBHttpClientConnection.java:172)
        at 
org.apache.http.impl.conn.CPoolProxy.receiveResponseEntity(CPoolProxy.java:157)
        at 
org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273)
        at 
org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123)
        at 
org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:254)
        at 
org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
        at 
org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
        at 
org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
        at 
org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
--=_alternative 006CEC6B85257D55_=--