[
https://issues.apache.org/jira/browse/SOLR-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903559#comment-13903559
]
Shawn Heisey commented on SOLR-5604:
------------------------------------
bq. What prevents you from keeping a reference to the connection manager along
with that to HttpClient? Connection pools are separate entities. They have
their separate life cycles and can be shared by multiple clients. One can
create a new client that makes use of an existing connection pool.
When I first started looking at this, I didn't see any way to set these options
with the interface -- HttpClientConnectionManager. When I looked deeper I
found PoolingHttpClientConnectionManager, where it is possible to set the
connection limits after creation. There will be some restrictions, but i think
that means that I can maintain the connection limit setters.
I may be able to get a little further with this now. I need to look deeper
into the docs.
> Remove deprecations caused by httpclient 4.3.x upgrade
> ------------------------------------------------------
>
> Key: SOLR-5604
> URL: https://issues.apache.org/jira/browse/SOLR-5604
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 4.7
> Reporter: Shawn Heisey
> Fix For: 4.7, 5.0
>
> Attachments: SOLR-5604-4x-just-lucene.patch
>
>
> SOLR-5590 upgraded httpclient in Solr and Lucene to version 4.3.x. This
> version deprecates a LOT of classes and methods, recommending that they all
> be replaced with various methods from the HttpClientBuilder class.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
