RE: Memory leak in CloseableHttpAsyncClient?

2016-10-17 Thread Rob Griffin
I've raised the issue https://issues.apache.org/jira/browse/HTTPASYNC-116 Regards, Rob Griffin Software Analyst, Spotlight on SQL Server Dell Software | R & D office +613 9811 8021 -Original Message- From: Oleg Kalnichevski [mailto:ol...@apache.org] Sent: Monday, 17 October 2016

AW: Controlling releaseConnection

2016-10-17 Thread ecki
Hello, Can younspecify why you need to delay it? Do wou want to make some kind of rate limit with this or optimize pipelining? Gruss Bernd -- http://bernd.eckenfels.net >From Win 10 Mobile Von: Pellerin, Clement Gesendet: Montag, 17. Oktober 2016 23:23 An: httpclient-users@hc.apache.org

Re: Controlling releaseConnection

2016-10-17 Thread Shawn Heisey
On 10/17/2016 3:22 PM, Pellerin, Clement wrote: > Our customer needs to delay the release of the connection until the response > is fully processed. > They want to turn off the early automatic release of the connection and do it > manually later. > > This is the problematic code in

Re: Disabling pooling of PoolingConnectionManager

2016-10-17 Thread Murat Balkan
I see. I think that also means that I cannot share the ClosableHttpClient instance among multiple threads as each client can refer to one connection manager instance. Can connectionreusestrategy be used so that the pooling connection manager will always return a new connection regardless of the

Re: Disabling pooling of PoolingConnectionManager

2016-10-17 Thread Bhowmik, Bindul
Murat, On Mon, Oct 17, 2016 at 8:11 PM, Murat Balkan wrote: > I see. I think that also means that I cannot share the ClosableHttpClient > instance among multiple threads as each client can refer to one connection > manager instance. > > Can connectionreusestrategy be used so

Re: Disabling pooling of PoolingConnectionManager

2016-10-17 Thread Bhowmik, Bindul
Murat, On Mon, Oct 17, 2016 at 11:12 AM, Murat Balkan wrote: > Hi, > > We are using PoolingHttpClientConnectionManager to open up connections to > multiple URL's in different threads (via different HttpGet objects). > > The only reason we are using the

Re: Memory leak in CloseableHttpAsyncClient?

2016-10-17 Thread Oleg Kalnichevski
On Sun, 2016-10-16 at 21:54 +, Rob Griffin wrote: > We are using HTTPAsynchClient to send data to our web site from a Java > client. > > We call CloseableHttpAsyncClient.execute() to execute HTTP PUTs at the rate > of several hundred per minute. Sometimes our web site slows down and does

Disabling pooling of PoolingConnectionManager

2016-10-17 Thread Murat Balkan
Hi, We are using PoolingHttpClientConnectionManager to open up connections to multiple URL's in different threads (via different HttpGet objects). The only reason we are using the PoolingHttpClientConnectionManager is its' performance in multi-thread environments (as suggested by the

Re: Disabling pooling of PoolingConnectionManager

2016-10-17 Thread Murat Balkan
Hi Bindul, Thanks for the answer. I was thinking that using a shared connection manager will increase the performance. What will be the implications of reusing the same BasicHttpClientConnectionManager instance? Regards, Murat On Mon, Oct 17, 2016 at 2:31 PM, Bhowmik, Bindul

Re: Disabling pooling of PoolingConnectionManager

2016-10-17 Thread Bhowmik, Bindul
Murat, On Mon, Oct 17, 2016 at 12:58 PM, Murat Balkan wrote: > Hi Bindul, > Thanks for the answer. > I was thinking that using a shared connection manager will increase the > performance. What will be the implications of reusing the same > BasicHttpClientConnectionManager

Controlling releaseConnection

2016-10-17 Thread Pellerin, Clement
We are using HttpClient 4.5.2 Our customer needs to delay the release of the connection until the response is fully processed. They want to turn off the early automatic release of the connection and do it manually later. This is the problematic code in MainClientExec // check for