[
https://issues.apache.org/jira/browse/SOLR-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sami Siren resolved SOLR-861.
-----------------------------
Resolution: Fixed
Fix Version/s: (was: 4.1)
4.0-BETA
I have not heard back anything that suggests that the shutdown() does not do
it's job. resolving this one as fixed (the work was done in SOLR-2020,
SOLR-3532).
> 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-BETA
>
> 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
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]
