[
https://issues.apache.org/jira/browse/SOLR-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291678#comment-13291678
]
Sami Siren commented on SOLR-861:
---------------------------------
bq. it's not clear to me if this has already been addressed by the new client
in SOLR-2020 - can you please triage for 4.0?
I have not done anything specific to address this issue. Since opening this
issue a shutdown() method was added in HttpSolrServer that should take care of
releasing the resources, if that's not working then there's a bug.
> SOLRJ Client does not release connections 'nicely' by default
> -------------------------------------------------------------
>
> Key: SOLR-861
> URL: https://issues.apache.org/jira/browse/SOLR-861
> Project: Solr
> Issue Type: Bug
> Components: clients - java
> Affects Versions: 1.3
> Environment: linux
> Reporter: Ian Holsman
> Assignee: Sami Siren
> Fix For: 4.0
>
> Attachments: SimpleClient.patch
>
>
> as-is the SolrJ Commons HttpServer uses the multi-threaded http connection
> manager. This manager seems to keep the connection alive for the client and
> does not close it when the object is dereferenced.
> When you keep on opening new CommonsHttpSolrServer instances it results in a
> socket that is stuck in the CLOSE_WAIT state. Eventually this will use up all
> your available file handles, causing your client to die a painful death.
> The solution I propose is that it uses a 'Simple' HttpConnectionManager which
> is set to not reuse connections if you don't specify a HttpClient.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
