Intresting... I'd suggest to return 200 with XML-Response in case of any SOLR-related problem (and leave some job to Tomcat).
Of course if our crawler do not use 'If-modified-since' (such HTTP should be handled by 'front-end'/httpd/firewall/proxy before reaching JEE/SOLR container)... We are mixing different transport layers... RMI-IIOP does not use HTTP codes to pass Java Exceptions to remote client... >Speaking as a former web spider maintainer, it is very important to keep >the HTTP response codes accurate. Never return an error with a 200. >If we want more info, return an entity (body) with the 400 response.
