You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2015/02/11 09:31:13 UTC
[jira] [Updated] (HTTPCORE-369) Release BasicNIOConnPool
connections per HttpHost
[ https://issues.apache.org/jira/browse/HTTPCORE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski updated HTTPCORE-369:
---------------------------------------
Fix Version/s: (was: 4.4)
4.4.1
> Release BasicNIOConnPool connections per HttpHost
> -------------------------------------------------
>
> Key: HTTPCORE-369
> URL: https://issues.apache.org/jira/browse/HTTPCORE-369
> Project: HttpComponents HttpCore
> Issue Type: Improvement
> Components: Documentation, HttpCore NIO
> Affects Versions: 4.3
> Reporter: Michael Nitschinger
> Fix For: 4.4.1
>
>
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org