lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jake Brownell (JIRA)" <>
Subject [jira] Created: (SOLR-1546) When querying solrj the SolrServerException's cause is null
Date Sat, 07 Nov 2009 00:27:32 GMT
When querying solrj the SolrServerException's cause is null

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

        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

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.


This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message