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

Anand commented on SOLR-4451:
-----------------------------

Upgraded to Solr 4.2.1 today. Also, updated http components to the ones 
provided in the package (httpclient-4.2.3 and httpcore-4.2.2) and I was still 
seeing the error message "java.lang.NoSuchMethodError: 
org.apache.http.impl.conn.SchemeRegistryFactory.createSystemDefault()Lorg/apache/http/conn/scheme/SchemeRegistry;"
 Turns out the httpclient jar was conflicting with httpclient jar used by 
selenium tests. Once they were aligned,  things started looking a lot better.
                
> Upgrade to httpclient 4.2.x and take advantage of SystemDefaultHttpClient
> -------------------------------------------------------------------------
>
>                 Key: SOLR-4451
>                 URL: https://issues.apache.org/jira/browse/SOLR-4451
>             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...
> http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/impl/client/SystemDefaultHttpClient.html
> ...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: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to