You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2015/12/27 21:41:49 UTC

[jira] [Created] (SOLR-8469) Look into how HttpSolrCall#remoteQuery handles IOException and passing error messages back to a client.

Mark Miller created SOLR-8469:
---------------------------------

             Summary: Look into how HttpSolrCall#remoteQuery handles IOException and passing error messages back to a client.
                 Key: SOLR-8469
                 URL: https://issues.apache.org/jira/browse/SOLR-8469
             Project: Solr
          Issue Type: Bug
            Reporter: Mark Miller
            Assignee: Mark Miller


We have a test fail that is reported to the client as:

bq. Error from server at http://127.0.0.1:45745/awholynewcollection_0: non ok status: 500, message:Server Error

but problem seems to be:

bq. org.apache.solr.common.SolrException: Error trying to proxy request for url: http://127.0.0.1:45745/awholynewcollection_0/select
bq. Caused by: java.io.IOException: Response header too large
bq. Caused by: java.nio.BufferOverflowException

I'm not sure if this is because we are using sendError on catching Exception in that method instead of throwing out an exception (I'd like to make this change anyway), or if it's because we close the streams. I've removed those closes in another uncommitted issue about using method.abort().



--
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