if you use this constructor:
public CommonsHttpSolrServer(URL baseURL, HttpClient client)
then solrj never touches the HttpClient configuration.
I normally reuse a single CommonsHttpSolrServer as well.
On Jan 27, 2009, at 9:52 AM, Walter Underwood wrote:
Making requests in parallel, using the default connection manager,
which is multi-threaded, and we are reusing a single
CommonsHttpSolrServer
for all requests.
wunder
On 1/26/09 10:59 PM, "Noble Paul നോബിള് नो
ब्ळ्" <noble.p...@gmail.com>
wrote:
are you making requests in parallel ?
which ConnectionManager are you using for HttpClient?
On Tue, Jan 27, 2009 at 11:58 AM, Noble Paul നോബിള്
नोब्ळ्
<noble.p...@gmail.com> wrote:
you can set any connection parameters for the HttpClient and pass on
the instance to CommonsHttpSolrServer and that will be used for
making
requests
make sure that you are not reusing instance of CommonsHttpSolrServer
On Tue, Jan 27, 2009 at 10:59 AM, Walter Underwood
<wunderw...@netflix.com> wrote:
We just switched to Solrj from a home-grown client and we have a
huge
jump in the number of connections to the server, enough that our
load balancer was rejecting connections in production tonight.
Does that sound familiar? We're running 1.3.
I set the timeouts and connection pools to the same values I'd
used in my other code, also based on HTTPClient.
We can roll back to my code temporarily, but we want some of
the Solrj facet support for a new project.
wunder
--
--Noble Paul
