Just spit balling here, but we could add a ServletFilter that registers it's own LogHandler to record the last N messages above a certain severity, then configure that filter to intercept any requests for hte admin pages and if the SolrCore can't be accessed return a page listing those errors.
alternately -- register a custom error JSP which says "you encountered exception X, here are the last N exceptions that were logged which may have contributed to this..." : Date: Wed, 29 Nov 2006 09:54:37 -0500 : From: Yonik Seeley <[EMAIL PROTECTED]> : Reply-To: solr-dev@lucene.apache.org : To: solr-dev@lucene.apache.org : Subject: Re: XML config : : On 11/29/06, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: : > I agree that this is more serious, making critical exceptions or logs : > accessible from the HTTP interface could be good...but it can also be : > a security risk in some cases, you don't necessarily want to expose : > all error messages to the world. : : A big part of the problem is that configuration errors often keep the : SolrCore from loading, and the admin pages don't work without that. : That may be an area for improvement. : : -Yonik : -Hoss
