hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCORE-369) Release BasicNIOConnPool connections per HttpHost
Date Mon, 16 Dec 2013 09:12:07 GMT

    [ https://issues.apache.org/jira/browse/HTTPCORE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848942#comment-13848942
] 

Oleg Kalnichevski commented on HTTPCORE-369:
--------------------------------------------

Michael,
The use of JIRA for answering questions and design discussions is generally discouraged. Would
it be a big deal for you to subscribe to the dev@hc.apache.org or httpclient-users@hc.apache.org
list? I will happily answer your questions there. 

As to your question it is generally expected that keeping track of leased connections and
their release back to the pool be a responsibility of the consumer. However, one can iterate
through all entries leased from the pool, collect those entries that match a particular criterium
and release them from the pool.

For detailed discussion and follow-up questions let's take it to the mailing list.

Oleg    

> Release BasicNIOConnPool connections per HttpHost
> -------------------------------------------------
>
>                 Key: HTTPCORE-369
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-369
>             Project: HttpComponents HttpCore
>          Issue Type: Improvement
>          Components: HttpCore NIO
>    Affects Versions: 4.3
>            Reporter: Michael Nitschinger
>
> Hi Folks,
> I'm not sure if this is just missing in the documentation or if its not possible at all,
so I wanted to bring it up and discuss.
> I'm firing out requests through the BasicNIOConnPool and use a List<HttpHost> do
to that in a round-robin fashion - kinda. Now it could happen that this list changes so new
hosts get added or old nodes removed. Adding new ones is not a problem since sockets get opened
on the fly, but I'm worrying about removing them.
> Is there a way to release all open connections for a HttpHost? There is not much documentation
around releasing those and from the API docs I see its only possible through a PoolEntry,
but I have no clue how that maps to a HttpHost.
> And if that's not feasible or intended, what would be the correct way to do it?
> Thanks,
> Michael



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

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


Mime
View raw message