I am using solr/solrj 4.6.1 along with the apache httpclient 4.3.2 as part
of a web application which connects to the solr server via solrj
using CloudSolrServer(); The web application is wired up with Guice, and
there is a single instance of the CloudSolrServer class used by all inbound
requests.
On 2/13/2014 1:38 PM, Jared Rodriguez wrote:
I am using solr/solrj 4.6.1 along with the apache httpclient 4.3.2 as part
of a web application which connects to the solr server via solrj
using CloudSolrServer(); The web application is wired up with Guice, and
there is a single instance of the Clou
Thanks Shawn,
I just regressed to Solrj 4.6.1 with http client 4.2.6 and am trying to
reproduce the problem. Using YourKit to profile and even just manually
simulating a few users at once, I see the same problem of open sockets. 6
sockets opened to the solr server and 2 of them still open after
On 2/13/2014 3:17 PM, Jared Rodriguez wrote:
I just regressed to Solrj 4.6.1 with http client 4.2.6 and am trying to
reproduce the problem. Using YourKit to profile and even just manually
simulating a few users at once, I see the same problem of open sockets. 6
sockets opened to the solr server
Thanks for the info, I will look into the open file count and try to
provide more info on how this is occurring.
Just to make sure that our scenarios were the same, in your tests did you
simulate many concurrent inbound connections to your web app, with each
connection sharing the same instance of
On 2/14/2014 2:45 AM, Jared Rodriguez wrote:
> Thanks for the info, I will look into the open file count and try to
> provide more info on how this is occurring.
>
> Just to make sure that our scenarios were the same, in your tests did you
> simulate many concurrent inbound connections to your web
Jared,
I faced a similar issue when using CloudSolrServer with Solr. As Shawn
pointed out the 'TIME_WAIT' status happens when the connection is closed
by the http client. HTTP client closes connection whenever it thinks the
connection is stale
(https://hc.apache.org/httpcomponents-client-ga/tutori
Kiran & Shawn,
Thank you both for the info and you are both absolutely correct. The issue
was not that sockets were leaked, but that wait time thing is a killer. I
ended up fixing the problem by changing the system property of
"http.maxConnections" which is used internally to Apache httpclient t
