lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McKinley (JIRA)" <>
Subject [jira] Updated: (SOLR-179) Save me from myself! Abort on configuration errors
Date Tue, 27 Mar 2007 01:39:32 GMT


Ryan McKinley updated SOLR-179:

    Attachment: SOLR-179-ConfigurationErrors.patch

updated to apply cleanly with trunk.

I looked into having the SolrDispatchFilter.init() thow an exception that would hopefully
abort the web-app.  This works in Resin, but in Jetty it just logs the error and continues
normally -- at that point it gives a 404 for any request though.

rather then have undefined behavior, this caches the error string and spits it out for every

> Save me from myself!  Abort on configuration errors
> ---------------------------------------------------
>                 Key: SOLR-179
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Ryan McKinley
>             Fix For: 1.2
>         Attachments: SOLR-179-ConfigurationErrors.patch, SOLR-179-ConfigurationErrors.patch
> When something goes wrong in solr configuration, I want solr to stop working and loudly
say "something went wrong"  This patch adds a collection of severe errors to SolrConfig. 
If abortOnConfigurationError=true and there are errors, the SolrDispatchFilter prints out
a nice message saying "hey something went wrong!"
> The specific things that were hidden in error files that will now give dramatic error
>  * unknown class for RequestHandler/ResponseWriter
>  * any exception throw during handler/writer init()
> If you want to disable this behavior (perhaps for a production environment) you need
to add:
>   <abortOnConfigurationError>false</abortOnConfigurationError>
> to solrconfig.xml
> for more discussion, see:

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

View raw message