[
https://issues.apache.org/jira/browse/SOLR-14302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051473#comment-17051473
]
Ishan Chattopadhyaya commented on SOLR-14302:
---------------------------------------------
Ouch, just realized that I had omitted it. I think I mistook it for some CMS
specific parameter as it was under GC_TUNE.
No objection to bringing it back (so long as it doesn't go back to GC_TUNE
again. Thanks Hoss!
> Solr stops printing stacktraces in log and output due to
> OmitStackTraceInFastThrow - regression of SOLR-7436
> -------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-14302
> URL: https://issues.apache.org/jira/browse/SOLR-14302
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.1
> Reporter: Chris M. Hostetter
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
