You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2013/04/17 04:18:13 UTC
[jira] [Resolved] (SOLR-4487) SolrException usage in solrj client
code can't handle all possible http error codes returned by servers --
example "413 Request Entity Too Large"
[ https://issues.apache.org/jira/browse/SOLR-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-4487.
----------------------------
Resolution: Fixed
Fix Version/s: 5.0
Committed revision 1468705.
Committed revision 1468718.
> SolrException usage in solrj client code can't handle all possible http error codes returned by servers -- example "413 Request Entity Too Large"
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-4487
> URL: https://issues.apache.org/jira/browse/SOLR-4487
> Project: Solr
> Issue Type: Improvement
> Components: clients - java
> Affects Versions: 4.0
> Reporter: Alexander Dietrich
> Assignee: Hoss Man
> Fix For: 4.3, 5.0
>
> Attachments: SOLR-4487.patch
>
>
> Solr responds to excessively large queries with a 413 status code, but HttpSolrServer.request() loses this information when it tries to look up the code in SolrException.ErrorCode, resulting in a status code 0 in the thrown exception.
> Being able to see this status code would be helpful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org