[
https://issues.apache.org/jira/browse/SOLR-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072239#comment-15072239
]
Mark Miller commented on SOLR-8469:
-----------------------------------
If you test a similar exception coming out of something other than remoteQuery,
a more relevant message is returned - so something about the special case
IOException handling or something else in remoteQuery (like the steam closing)
is causing this.
> 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: [email protected]
For additional commands, e-mail: [email protected]
