I recently saw a person ask a question about an Exception in their logs that didn't have a stack trace even though it certainly seemed like it should.
I was immediately suspicious that they may have tweaked their solr options to override the -XX:-OmitStackTraceInFastThrow that was added to bin/solr by
SOLR-7436, but then i discovered it's gone now - removed in SOLR-13394 w/o any discussion/consideration (and possibly unintentionally w/o understanding it's purpose?)
We should almost certainly restore this by default.
- is broken by
SOLR-13394 Change default GC from CMS to G1
- is related to
SOLR-7436 Solr stops printing stacktraces in log and output