Thanks all for your responses. For some reason the emails were getting filtered out of my inbox.
*Otis* - jstack is a great suggestion, thanks! The problem didn't happen this morning but next time it does I will certainly get the dump to see exactly where the app is swimming around. I haven't used StreamingUpdateSolrServer but I will see if that makes a difference. Are there any major drawbacks of going this route? *Sami* - if you are referring to config:maxConnections=200&maxConnectionsPerHost=8, it showed up up in the Solr logs, not the SolrJ logs. The client IS instantiated only once and not for every request. I was curious if this was part of the problem. Do I need to re-instantiate the object for each request made? I figured there would be more overhead if I am re-creating the connection several times when I never really need to shut it down, but at this point the overhead would be minimal though so I will try that. *Hoss* - The reason it seemed the client was creating the log was because the indexer (solr *server*) was more or less dormant for several hours, then I booted up my indexing *client* and the maxConnectionsPerHost tidbit was spit out right away. I was looking for something in the solrconfig and online but didn't find anything. I didn't look for very long so will check it out again. Some very good suggestions here. I appreciate everyones feedback. I will follow up after some experimentation. Thanks, Briggs Thompson On Tue, Oct 9, 2012 at 11:19 AM, Chris Hostetter <hossman_luc...@fucit.org>wrote: > > : I did some digging and experimentation and found something interesting. > : When starting up the application, I see the following in Solr logs: > : Creating new http client, > config:maxConnections=200&maxConnectionsPerHost=8 > ... > : It seems as though the maxConnections and maxConnectionsPerHost are not > : actually getting set. Anyone seen this problem or have an idea how to > : resolve? > > To elaborate on sami's comment... > > If you are seeing this in the logs from your solr *server*, it is unlikey > that it has anything to do with the settings you are making on your solr > *client* .... this is probably related to the http client created inside > solr for communicating with other solr nodes (ie: replication, solr cloud > distributed updates, solr cloud peersync, etc...). Which is different > from the properties you set on the http client in your solr client > application. > > I believe there is a way to configure the defaults for the internal used > http clients via solrconfig.xml, but off the top of my head i don't > remember what that is. > > > > -Hoss >
