Hi, Solr runs in a servlet container (Jetty), and normally you want one webapp to not be able to cause issues for another one by e.g. running System.exit(). But Solr is different, it is the only servlet in the container, and in certain cases (such as syntax error in config files during startup), there are exceptions in the logs (such as ClassNotFound), Solr's servlet was never initialized, so returns a cryptic HTML page, while Jetty remains running.
Is there a way we could allow some classes responsible for bringing up Solr to call Jetty's life-cycle command to shut down the entire Jetty JVM? I don't think we should allow all plugins, 3rd party tools etc to do this, but our own bootstrapping and config parsing code. Jan --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
