lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sami Siren (JIRA)" <>
Subject [jira] [Commented] (SOLR-861) SOLRJ Client does not release connections 'nicely' by default
Date Fri, 08 Jun 2012 10:49:24 GMT


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:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message