lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Updated] (SOLR-4451) Upgrade to httpclient 4.2.x and take advantage of SystemDefaultHttpClient
Date Wed, 13 Feb 2013 03:01:13 GMT


Hoss Man updated SOLR-4451:

    Attachment: SOLR-4451.patch


* upgrades httpcomponents in ivy
* upgrades httpcomponents in maven pom (i think)
* switches from DefaultHttpClient to SystemDefaultHttpClient in solrj
* fixes some existing helper code that treats ThreadSafeClientConnManager as special to also
work with PoolingClientConnectionManager (all ClientConnectionManager impls are now thread
safe, and ThreadSafeClientConnManager has been deprecated with PoolingClientConnectionManager
as the recommended replacement)

...test and precommit all pass
> Upgrade to httpclient 4.2.x and take advantage of SystemDefaultHttpClient
> -------------------------------------------------------------------------
>                 Key: SOLR-4451
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>             Fix For: 4.2, 5.0
>         Attachments: SOLR-4451.patch
> HttpComponent is up to version 4.2, and included in 4.2 is a new subclass of DefaultHttpClient
named SystemDefaultHttpClient, which automatically configures itself using the "standard"
java system properties...
> ...i think we should upgrade and start using this new class in place of DefaultHttpClient,
so that SolrJ clients (and implicitly SolrCloud) can automaticly leverage system properties
users may expect to work.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message