[jira] [Commented] (SOLR-6561) LBHttpSolrServer's aliveCheckExecutor is leaking connection when ResponseParser is null

["Sudhan Moghe (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147375#comment-14147375 ] 

Sudhan Moghe commented on SOLR-6561:
------------------------------------

We have changed our handling and not setting parser to null. We are using a ResponseParser on the lines of NoOpResponseParser. So, this bug is not affecting us anymore.

> LBHttpSolrServer's aliveCheckExecutor is leaking connection when ResponseParser is null
> ---------------------------------------------------------------------------------------
>
>                 Key: SOLR-6561
>                 URL: https://issues.apache.org/jira/browse/SOLR-6561
>             Project: Solr
>          Issue Type: Bug
>          Components: clients - java
>    Affects Versions: 4.10
>            Reporter: Sudhan Moghe
>
> LBHttpSolrServer's aliveCheckExecutor is leaking connection when ResponseParser is null.
> We are providing search as a service and our Solr setup is not directly exposed to clients. We are setting parser to null and then passing on the InputStream, received from Solr server, as it is to our clients.
> The LBHttpSolrServer.checkAZombieServer() is no closing connection in this case.
> I think something like following needs to be there. Not the exact code.
> if (zombieServer.solrServer.getParser() == null)
> 	is = (InputStream) resp.getResponse().get("stream");
> 	is.close();
> }
> This is blocker for us. I will test this out locally and update this bug report. But, we can't deploy that in production till we get official fix.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org