[
https://issues.apache.org/jira/browse/SOLR-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581711#comment-14581711
]
Eirik Lygre commented on SOLR-7664:
-----------------------------------
See also
http://codingtricks.fidibuy.com/participant/join/54fce329b760506d5d9e7db3/Spring-Data-Solr-cannot-handle-long-queries
for another user who experienced the same problem.
> Solrj client throws ParseException("Illegal content type") when server
> returns "other http error" (here 413) with BinaryResponseParser
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-7664
> URL: https://issues.apache.org/jira/browse/SOLR-7664
> Project: Solr
> Issue Type: Bug
> Components: SolrJ
> Affects Versions: 5.2
> Reporter: Eirik Lygre
>
> We have a program that uses Solrj to index data. For some as-of-yet
> undetermined reason, the server returns "413 FULL Head" with no Content-Type
> header.
> When that happens, the Solrj library fails. In HttpSolrClient.executeMethod,
> two things happen:
> If there is no processor, then a RemoteSolrException is thrown, which is
> good. Ref
> https://github.com/apache/lucene-solr/blob/lucene_solr_5_2_0/solr/solrj/src/java/org/apache/solr/client/solrj/impl/HttpSolrClient.java#L493.
> However, with a processor, the code tries to call ContentType.parse() with
> the returned ContentType, which is null. This method throws a
> ParseException("Illegal content type"), which propagates to the client. The
> cause of the error is very much hidden now. Ref
> https://github.com/apache/lucene-solr/blob/lucene_solr_5_2_0/solr/solrj/src/java/org/apache/solr/client/solrj/impl/HttpSolrClient.java#L513.
> It would be nice if the client would throw a RemoteSolrException in this
> case, too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
