[
https://issues.apache.org/jira/browse/SOLR-14302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris M. Hostetter updated SOLR-14302:
--------------------------------------
Attachment: SOLR-14302.patch
Assignee: Chris M. Hostetter
Status: Open (was: Open)
Attaching proposed fix that adds {{-XX:-OmitStackTraceInFastThrow}} directly to
SOLR_START_OPTS with a comment, users that don't care about having readable
error messages can override by setting {{-XX:+OmitStackTraceInFastThrow}} in
SOLR_OPTS, or with the "-a" command line option, etc...
feedback (particularly of the solr.cmd changes i have no ability to test)
requested asap in the hopes that we can included this fix in 8.5.
> 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
> Assignee: Chris M. Hostetter
> Priority: Major
> Attachments: SOLR-14302.patch
>
>
> 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
