On Mon, 2014-12-15 at 15:41 +, Maurice MILLS wrote:
> I am using HttpComponents 4.3.1 in my project and have recently run into a
> problem where PoolingHttpClientConnectionMananger is leaking HTTP
> connections. Normally this doesn't pose a problem because they are cleaned
> up after 60 sec
I spent a little time working through the documentation on the ldap protocol,
but I didn't find much on the topic.
Does the client have a way to plug in an external protocol handler, such
dsmlv2, where an ldap call (ldap://stuff) returns with xml (directory services
markup language flavor)?
Th
Hello Oleg,
I'm sorry, I misstated the problem. The problem is that in the sequence below,
the connection is closed and not put back into the pool for reuse (which
remains open until it is closed after the TIME_WAIT expires).
How can I just put the connection back into the list of available co
On December 16, 2014 5:52:16 PM GMT+01:00, Maurice MILLS
wrote:
>Hello Oleg,
>
>I'm sorry, I misstated the problem. The problem is that in the
>sequence below, the connection is closed and not put back into the pool
>for reuse (which remains open until it is closed after the TIME_WAIT
>expires).
I don't want to put an invalid connection back into the pool. I want to put
the connection I just finished using, that should still be valid, back into the
pool so I can reuse it again.
-Original Message-
From: Oleg Kalnichevski [mailto:ol...@apache.org]
Sent: mardi 16 décembre 2014 18
Connmgr.releaseConnection
Sendt fra min iPhone
> Den 16. des. 2014 kl. 18.25 skrev Maurice MILLS
> :
>
> I don't want to put an invalid connection back into the pool. I want to put
> the connection I just finished using, that should still be valid, back into
> the pool so I can reuse it aga
Below is a unit test that attempts to use the
"SSLConnectionSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER" option. It never
works and the wire level debug indicates that HC is always using
"BrowserCompatHostnameVerifier" instead. Can someone explain why or where my
code is incorrect?
WIRE LEVEL
Thank You for the quick response. Can we get a confirmation that this issue
is resolved in later versions or a probable solution can be designed for
the described scenario? The reason we ask is our product bundled
v4.2.5(upgraded from 3.1) of the library in April 2013 and moving to
4.3/4.4 would me
