[
https://issues.apache.org/jira/browse/SOLR-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl closed SOLR-1546.
-----------------------------
Resolution: Incomplete
Closing very old issue. If you still face such issues with latest version of
Solr, please open a new issue.
> When querying solrj the SolrServerException's cause is null
> -----------------------------------------------------------
>
> Key: SOLR-1546
> URL: https://issues.apache.org/jira/browse/SOLR-1546
> Project: Solr
> Issue Type: Improvement
> Components: clients - java
> Affects Versions: 1.4
> Environment: solrj
> Reporter: Jake Brownell
> Priority: Minor
>
> Our application processes queries like so:
> {code}
> try {
> final SolrServer server = getServer();
> final QueryResponse resp = server.query(query);
> return resp;
> } catch (final SolrServerException e) {
> /// bad things probably happened, invoke error processing and
> possibly switch to the backup
> }
> {code}
> Given SOLR-874 with dismax queries sometimes causing ParseException from
> Lucene, I'd like to be able to interrogate the cause chain of the
> SolrServerException. For example if I found ParseException in the chain, I
> could provide a specific error message and know that it's not necessary to
> switch to the backup server.
> As it is now, getCause is giving null. The undesirable fix right now is
> looking inside the toString/description for the "ParseException" phrase.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
