Interestingly it was SOLR-179 (Ryan M) that added the prevention of
error propagation because the idea was to start anyway and display a
webpage of the error. But it was later partially undone by SOLR-1846
(Hossman), albeit left this bit, probably by mistake -- an oversight.
Because it didn't quit
I would be surprised if my refactor caused a change in this behavior.
All I did was move some initialization out into a
ServeletContextListener. If I did cause such a change, that would be
unintended.
>From the perspective of a web application container (which is what
Jetty is). There's no reason
I noticed (as well as my colleague Vincent and with more detail and
root causing) that if Solr's CoreContainer has some issue starting up
for almost any reason, that it only logs an error (in
SolrDispatchFilter). From Jetty’s perspective, startup has succeeded,
thus the server is running. Seeing
